Healthcare is one of those domains where bad UX has real consequences. A confusing appointment flow doesn't just frustrate a user — it might mean they delay seeing a doctor. That weight was present throughout the Meril project, and it made the work feel meaningful in a way that's hard to replicate.
I worked on Meril as one of two frontend developers on a five-person team — two backend, two frontend, and a shared goal of building something that genuinely improved how patients and doctors connect.
How the Team Was Structured
The backend developers handled the complex integrations — data architecture, API endpoints, authentication, and the reliability layer that makes a healthcare app trustworthy. Their work was the foundation everything else sat on.
On the frontend, my co-developer and I focused on translating that foundation into an experience that felt effortless. In healthcare, the interface isn't decoration — it's the product. A patient booking an appointment needs clarity at every step. A doctor reviewing their schedule needs density without clutter. These are different needs, sometimes in tension, and designing for both simultaneously was the central creative challenge.
What I Focused On
My contributions centred on the UI and the appointment scheduling flow — one of the most critical features in any doctor-patient platform. Scheduling has to handle edge cases gracefully: unavailable slots, cancellations, rescheduling, time zones, different appointment types. Making all of that feel simple from the user's side requires careful thought underneath.
I also brought user-centric thinking into team discussions — advocating for interface decisions based on how real users would navigate the app, not just what was easiest to build.
Five Months on a Healthcare Product
This was the most collaborative project I'd worked on at that point. Five people with distinct responsibilities, working toward a shared release. It sharpened my ability to work across the frontend-backend boundary — understanding what the backend needed from us in terms of data handling, and communicating clearly about what the UI required from their endpoints.
Shipping a healthcare app raised the bar for quality in a way I hadn't experienced before. Edge cases that might be acceptable in other contexts simply aren't when someone's medical appointment is on the line.
This was a private company project — code and screenshots remain confidential.