Navigation flow
Forward and back navigation, persistent bottom tabs, and a coherent seven-screen customer journey.
LankaCare is a fictional Sri Lankan medical-centre app created to demonstrate how I design and build connected native mobile flows—not just isolated screen mockups.
This app runs locally on an Android emulator. Every doctor, medical centre, patient, time slot, fee, and appointment is fictional local demo data.
The prototype moves from specialty and doctor discovery through doctor details, channeling-time selection, patient information, a required demo notice, confirmation, appointments, and profile settings.
Selections and form values persist through local React state, and a completed simulated channeling appears in “Appointments.” The data layer is separated from the interface so the same screens can later connect to an API without redesigning the patient journey.
Captured from the working React Native app on an Android emulator. The small gear at the screen edge is an Expo development control, not part of the app interface.







Forward and back navigation, persistent bottom tabs, and a coherent seven-screen customer journey.
Selectable doctors, dates, time slots, patient fields, validation, settings, and saved appointment state.
Shared headers, cards, buttons, fields, summaries, navigation, and responsive native layouts.
Typed mock data and UI state are kept separate, ready to be replaced by real doctor, availability, and channeling APIs.
The prototype intentionally excludes real authentication, hospital records, databases, payments, notifications, patient data, and app-store distribution.
When “Channel doctor” is tapped, the app explicitly states: “Demo only — booking is simulated and not submitted.”
I can help turn a workflow into a focused mobile prototype or first working version with the right screens and states.