Discovery and browse
Patients browse hospitals, doctors, specialties, and test labs from their phone.
- Home, search, and category navigation
- Nearest-hospital sorting
- Provider imagery with remote media
- Home
- Patient Apps
iOS + Android
The patient journey, native on both platforms
Patients find a provider, book and pay, attend the visit, and follow their tests to a result — in a SwiftUI app on iOS and a Kotlin and Jetpack Compose app on Android.
- SwiftUI on iOS
- Kotlin + Compose on Android
- Five main patient tabs
Core journeys
Six areas of real workflow depth
The apps carry the visit past the confirmation screen, which is where most booking tools stop.
Booking and payment
Appointment creation is wired to live availability and protected payment flows.
- Multi-step doctor booking
- Razorpay-backed paid actions
- Quote-aware reschedule and cancel
Appointments and tests
The journey continues after booking instead of ending at a confirmation.
- Upcoming, sessions, cancelled views
- Requested through completed tests
- Linked diagnostics states
Profile and trust
Account behaviour includes meaningful profile completion and day-to-day convenience.
- Medical history completion
- Biometric login on iOS
- Theme override and maintenance gating
Diagnostics visibility
Tests are a dedicated patient surface, not a detail buried in an appointment.
- Request detail and coverage
- Unread result cues
- Status sync across linked bookings
Mobile polish
Small behaviours that make the apps feel finished rather than prototyped.
- Pull-to-refresh on appointments
- Keyboard done action on iOS
- Provider lookup optimisation
Money handled carefully
Paid actions verify before they commit
Payment is not an afterthought bolted onto booking. A paid action is verified first, and any charge for changing plans is quoted before the appointment moves.
- Payment before booking The guard runs ahead of appointment creation, not after.
- Quote-aware changes Cancel and reschedule charges are shown, then applied.
- Consistent with the portal The same rules the web surfaces enforce.
Two apps, one product
Parity where it counts
Both apps are real patient products backed by the same API and the same booking, diagnostics, and notification rules.
iOS
SwiftUI app covering booking, tests, biometrics, notifications, payments, and maintenance gating.
Android
Kotlin and Jetpack Compose app delivering the full patient booking journey.
Shared
Payments, diagnostics, booking windows, and status updates aligned with backend logic.
See the patient apps on a real device
We will walk a booking, a payment, and a linked test request end to end on both platforms.