One prototype, one week, and a health app people actually come back to.

Written for clinicians, understood by no one else.

Most health information is written by clinicians, for clinicians: dense, jargon-heavy, and built for a system, not a person trying to understand their own body. For the millions of people who don’t speak the language medicine defaults to, that gap isn’t an inconvenience, it’s a wall.

The scope of what needed covering was enormous: 26 medical specialties, from cardiology and neurology to genetics and infectious disease, each with its own vocabulary and its own way of intimidating a first-time reader. Flattening all of that into something a non-clinician could pick up in a five-minute lesson, without stripping out the accuracy that makes it trustworthy, was the real design problem, not just making it look nicer.

The starting point was a bare-bones FlutterFlow prototype, a shell of an idea and not yet a product. There was no visual system, no content structure, and no mechanism to make a habit out of something people otherwise avoid. The job was to turn it into something people would trust with their health, and actually come back to.