BeDry · Pediatric Health · Mobile · Web · API
From a validated MVP to a bladder-health platform.
Four years ago BeDry started as a single MVP. After it proved the idea, we rebranded it top to bottom and rebuilt it as a cross-platform product — now shipping advanced bladder-habit tools that help families understand and build healthier routines, all from one team.
The brief
BeDry is a pediatric bladder- and bowel-health product founded by a pediatric nephrologist. Parents log a child's fluid intake, urinations, leaks and stool habits; the app turns that diary into a structured summary a doctor can actually read.
What families track here is sensitive and clinical. The product had to be dependable, private and always current on both app stores — not a one-off build abandoned six months after launch, but a mobile core the business could grow on for years.
The client
Budi suh d.o.o. — a Croatian health company founded by pediatric specialists (nephrology, gastroenterology, urology). EM2 has been the standing product & engineering team since day one.
The journey
Four years,
three chapters.
Prove the idea
We started with a focused MVP — a digital bladder diary — to validate whether families and clinicians would actually use it in place of paper.
Rebrand & rebuild
With the concept proven, we did a complete rebranding into BeDry — new identity, the Pishko mascot, a fresh product language — and re-architected it as a true cross-platform app.
Build the habits layer
Current development goes beyond logging: advanced tools that read a child's bladder habits, coach healthier routines and track progress over time.
The partnership
The people who shipped the MVP are the ones building the platform today.
Not a vendor handing off a build, but a standing team across four years — every new feature scoped and quoted as its own fixed offer. The codebase gets healthier every year, not messier — and each new feature ships to iOS and Android at the same time, from the same source.
What we're building now
Bladder Habit Builder —
from diary to daily habits.
The free diary answers what happened. The habit layer, built with pediatric specialists, answers what to do about it — turning weeks of entries into a score, a plan and a trend line parents can follow.

Understand the habits
Turns diary entries into an easy-to-read Bladder Score and plain-language insights — leaks, drinking, bedwetting, stool — so families see what deserves attention.

Build the routine
A personalized bladder-training plan with drinking, urination and bowel schedules plus reminders — the habit-tracker layer that guides families day to day.

Follow the progress
Bladder capacity, nocturnal patterns and control tracked over time, so parents — and their doctor — can see routines actually working.
A sibling platform
CORTEX — a separate build for the same client.
Beyond BeDry, we're also building CORTEX for the same client — a standalone platform (not part of the BeDry app) for secure, end-to-end-encrypted consultations with verified experts. It's early stage, but it shares the trust we've earned over four years.
Its own platform
A distinct product with its own roadmap — connected to BeDry only where it makes sense, never merged into it.
Private by design
End-to-end-encrypted, zero-knowledge messaging: content is encrypted on-device and the server can never read it.
Same team, same standard
Built by the same standing EM2 team, applying what four years on BeDry taught us about health-grade software.
The approach
Built to last,
not just to launch.
One codebase, both stores
React Native + Expo ship natively to iOS and Android — every feature lands on both platforms at once, with no divergent forks to maintain.
A platform, not just an app
A Spring Boot API, an Angular web app for clinicians and a Next.js marketing site surround the mobile core — all sharing one data model and one auth flow.
Diary in, clinical report out
The app turns everyday logging into a structured medical summary — bladder capacity, nocturnal diuresis, Bristol stool scale — shareable straight to the doctor.
A standing team, not a vendor
The partnership pays for itself: the same engineers across four years — feature by feature, offer by offer — mean fewer regressions and institutional memory that compounds.
The build
One product,
many surfaces.
The same account and data flow across the mobile apps and the web app at bedry.app — a parent logs on the phone, a clinician reviews in the browser.






The result
Four years in and counting.
Stack — React Native · Expo · Angular · Next.js · Spring Boot · PostgreSQL · Docker