We also set up hypothesis tables and prioritization maps to keep the team aligned—basically making sure we weren’t just building cool features but solving real user and business problems.
We kept things scrappy but structured, running lightweight design sprints so we could move fast without losing focus:
Mapping the App – First, we sketched out the Information Architecture basics: Home, Notifications, Care, Community, Shop, Profile. Just the bare bones so everyone was aligned.
Prototyping – We started super rough with low-fidelity flows, then quickly turned them into clickable Figma prototypes so we could put something in front of users fast.
Testing & Iterating – We ran quick sessions to watch where people stumbled (spoiler: the medical jargon and multi-step flows tripped almost everyone up). From there, we stripped things down, rewrote terms, and made interactions more direct.
Refining with Accessibility – Instead of leaving accessibility for last, we baked in WCAG 2.1 compliance as part of the polish. That meant clearer language for readability, stronger contrast ratios, bigger tap targets, and adding proper labels/alt text so the app worked well with screen readers.
We ended up creating a set of features that felt both practical and human.
Users could report their symptoms in whatever way worked best for them—typing in a search, tapping an affected area on the body, or sliding on a pain scale. All of that fed into a Weekly Health Report, which turned messy health data into a clean, easy-to-read dashboard.
To make sure people didn’t feel isolated, we built a Community space with reels and posts where users could learn, share, and connect around health topics.
And finally, we added a Shop for remedies, where users could buy supplements that were actually tied to their health profile—so it wasn’t just another marketplace, it was personalized care.
By applying strategies like information hierarchy and contextual grouping, we created an experience that empowers users to confidently take control of their health without cognitive overload or decision fatigue.
Conclusion
For me, the biggest takeaway was that balancing rigorous research with lean, fast-moving design sprints is what made this possible. By keeping methods lightweight but grounded in real data, we stayed aligned as a team, built stakeholder trust, and delivered something that genuinely worked for people.
Copyright 2025 Miyya Cody