sManager

Problem
The app needed to move from native Android to Flutter without pausing the feature pipeline for a rewrite.
Approach
An incremental multi-module migration with native-to-Flutter bridging, so both stacks shipped side by side through the whole transition.
Outcome
1M+ downloads, 5,000+ daily active users, and 99.8% crash-free users sustained through the migration
1M+ downloads · 5,000+ DAU · 99.8% crash-free
SManager is how a small Bangladeshi business runs its day: daily sales, balance, digital payment collection, installment sales, stock, and growth reports. The engineering story is the migration. Rewriting it would have frozen the feature pipeline for months, so instead the app moved to Flutter module by module, with native and Flutter running side by side and bridging between them. It kept shipping the whole way, at over a million downloads and a sustained 99.8% crash-free rate.
What I did
- Chose an incremental multi-module migration over a rewrite so the feature pipeline never paused — the app kept shipping through the entire native-to-Flutter transition at 1M+ downloads, 5,000+ daily active users, and 99.8% crash-free users sustained.
- Directed 8 engineers alongside QA, PM, and UI/UX, owning delivery from BRD and PRD through UAT, plus feature breakdown, feasibility analysis, and application performance.
- Built the POS module in Flutter, fully offline-first — sales, stock, and payments captured with no connection and reconciled on reconnect — with offline caching across the app’s other flows.
- Established the testing practice — every release exercised as an end user across a device matrix, reproducing the scenarios the product actually hit in the field rather than the happy path.
Stack
Screens



More work
MobileSheba.xyz
The customer app for Bangladesh’s largest home-services marketplace.
MobileVWB — Vulnerable Women Benefit
The World Food Programme mobile app for a national social-protection programme supporting vulnerable women across Bangladesh.
MobileeKYC in Bashundhara Pocket · Knower · Ami Probashi SDK · Paperless
Third-party integrations delivered inside other companies’ codebases and release cycles, plus the cross-team engineering work that runs alongside them.
Building something that needs this kind of engineer?
Hiring, contract, or an architecture problem — tell me the shape of it and I’ll come back with something specific.