Skip to content
yashraj.
[ Case study · 01 of 03 · Maternal Health · Mobile ]

iMumz 

A pregnancy app, rebuilt to scale to 100K+ mothers.

Client
iMumz
Role
Software Engineer II · Mobile Lead
Year
2024 — Present
Duration
2+ years (ongoing)
Share
iMumz
Maternal Health · Mobile2024 — Present
[ Overview ]

The brief, in a paragraph.

iMumz needed to scale their pregnancy wellness app to serve over 100K expecting mothers across India while maintaining a crash-free, performant experience. The existing codebase had stability issues causing user drop-off, and new engagement features needed to be shipped rapidly without breaking the core experience. The team required engineering leadership to own the mobile platform end-to-end.

100K+
Active mothers
+38%
Crash-free sessions
+25%
Engagement lift
Release velocity
[ 01 · Problem ]

Every project has a story before it has a solution. Here's the part nobody writes on the case-study cover.

Stability was eroding trust release after release.

iMumz needed to scale their pregnancy wellness app to serve over 100K expecting mothers across India while maintaining a crash-free, performant experience. The existing codebase had stability issues causing user drop-off, and new engagement features needed to be shipped rapidly without breaking the core experience.

  • 01Crash-prone codebase causing silent user churn at scale
  • 02Multiple state-management styles drifting in the same app
  • 03No A/B framework — every product call was an opinion
  • 04Manual releases with multi-day cycle times and rollback fear
[ 02 · Approach ]

Architect, instrument, then ship.

Took full ownership of the Flutter mobile platform as Software Engineer II. Refactored the architecture to BLoC pattern for predictable state management, implemented comprehensive Crashlytics monitoring, and established automated CI/CD pipelines with Fastlane and GitHub Actions. Led the development of A/B testing infrastructure that enabled data-driven feature rollouts.

/01

BLoC as the only state pattern

One predictable mental model across the app. Removed two competing patterns over six weeks of patient migration.

/02

Crashlytics on every critical path

Every navigation transition, payment hop, and content load got telemetry. Issues surfaced in hours, not weeks.

/03

A/B testing pipeline

Built a Firebase Remote Config + analytics pipeline so every product hypothesis was a measurable bet, not a meeting.

/04

Fastlane + GitHub Actions CI/CD

Push to main → versioned build on Play Console → staged rollout. Released Friday afternoon with confidence.

[ 03 · Solution ]

A platform engineered to ship — not just to run.

What we built isn't a single feature; it's a way of working. Every feature now lands instrumented, tested, and behind a remote flag. Every developer can ship to staging without asking permission.

  • 01Migrated 60% of screens to BLoC over 6 sprints, no regressions
  • 02Crash-free sessions improved to 99.2% across iOS + Android
  • 03Built 14 A/B experiments that ran without engineering involvement
  • 04Halved the average bug-to-fix-to-release cycle
  • 05Mentored two junior developers from feature work to ownership
01Onboarding
02Daily content
03Yoga sessions
[ 04 · Results ]

The numbers, after the dust settled.

+38%
Crash-free sessions

From a baseline 96.4% to 99.2% — sustained over 14 releases.

+25%
Engagement

A/B-tested onboarding lifted DAU/MAU ratio across cohorts.

100K+
Active mothers

Sub-2-second cold starts even on low-end Android devices.

Release velocity

Cut the average release cycle from 8 days to 4.

[ 05 · Before vs after ]

What changed, measured.

MetricBeforeAfter
Crash-free sessions96.4%99.2% (sustained over 14 releases)
Release cycle time8 days, manual, multi-stage4 days, automated via Fastlane + GitHub Actions
State management3 competing patterns drifting across the app1 (BLoC), with 60% of screens migrated in 6 sprints
A/B experiments running without engineering014, via Firebase Remote Config + analytics pipeline
[ 06 · Stack ]

What it's built with.

Mobile
  • Flutter
  • Dart
  • BLoC
  • Riverpod (gradual)
Backend
  • Firebase
  • REST APIs
  • Remote Config
Quality
  • Crashlytics
  • Unit Tests
  • Widget Tests
Delivery
  • Fastlane
  • GitHub Actions
  • Play Console

Yashraj consistently demonstrates full ownership of projects, ensuring timely delivery with precision and attention to detail.

Aankit Roy
Engineering Leader · iMumz
[ Need similar work? ]

I build Flutter apps, Next.js websites, and full-stack products for ambitious teams.

[ Build something like this ]

Got a problem with this shape?

Most engagements start with a thirty-minute conversation. Tell me what you're building and what hurts.