Overview
CresciBimbo keeps a newborn's growth, feeding, sleep, nappies and medical visits in one place, and turns them into readable trends and a report parents can bring to the paediatrician.
Problem
New parents log dozens of small events a day across notes, chats and memory. The information exists, but it is scattered, hard to read over time and hard to share at a check-up.
My role
I own the product end to end: definition, UX, architecture, development, QA, Play Store policy compliance and release configuration.
Challenges
- Work reliably offline — at 3 a.m., with one hand free.
- Keep family data private while still offering secure sign-in.
- Turn raw logs into trends and a report a doctor can actually use.
- Meet Google Play policy requirements for an app that handles health-related data.
Solution
An offline-first app: every event is written to a local database first and the interface reacts to state changes immediately. A dashboard summarises the day, charts show growth over time, and one tap exports a PDF report.
Architecture & approach
- Flutter UI with Riverpod for predictable, testable state.
- Isar as the local NoSQL store — no network needed to log an event.
- Firebase Authentication for account access.
- On-device PDF generation for medical reports.
- Releases through Google Play Console testing tracks.
Technology
Outcome
Released on Google Play. A complete product loop — idea, design, build, QA, policy review and release — run by one person.
Lessons learned
- Offline-first is a product decision before it is a technical one.
- Policy and compliance work belongs in the plan, not at the end.
- Small, frequent releases keep the scope honest.