Two apps, one codebase
Two patient groups, two visual identities, one government timeline. Built as separate codebases, every screen, fix, and review would have happened twice.
Poland's National Health Fund needed two patient apps for its POZ Plus programme: chronic-disease care and physiotherapy. We shipped both from one Flutter codebase.


moje zdrowie+ · moje fizjo+ - one ui kit, two identities
Shared packages carry the UI and the data layer. A change lands once and ships twice - to both apps, on both platforms.
Two patient groups, two visual identities, one government timeline. Built as separate codebases, every screen, fix, and review would have happened twice.
Chronic care runs on data patients already track - blood pressure, activity, sleep - but it lives in HealthKit on iOS and Google Fit on Android, in different shapes.

the medication module · synced nightly, counted down daily
The core users are older patients managing chronic conditions. Default mobile UI conventions - small type, low contrast, gesture-heavy navigation - quietly exclude exactly that group.

pain before, pain after · therapy that reports back

The engineers who shipped both apps answer the contact form.