About This Project
SaathMera helps elderly parents get care at home while their children, often in another city, stay informed. One combined Android app serves two roles. The elderly member books a doctor or nurse home visit, a doctor video call on WhatsApp or a blood test at home, and answers a one-tap daily check-in. A linked family member sees those answers, gets an alert when a parent says Not Good or misses a check-in, and can book care on the parent's behalf. The interface is built for older adults first: large type, large tap targets, plain words, one primary action per screen, and an emergency button that calls a chosen contact without menus. Every booking shows where it stands, from request to confirmation to the completed visit, so nobody has to chase the care team. SoftwareCrafting designed and built the product end to end: the brand, the interface and design system, the Expo React Native app, the Node.js and PostgreSQL backend, the operations panel and the public website. Every screen in this case study uses fictional sample data. No patient information is shown.
Key Features
- Elderly and family roles in one Android app
- One-tap daily check-in with family alerts
- Doctor and nurse home visit booking
- Doctor video call on WhatsApp
- Blood test sample collection at home
- Booking status from request to completed visit
- Family linking with the parent's approval
- Booking care on a parent's behalf
- One-button emergency call to a chosen contact
- Care plans, entitlements and online payments
- Daily wellness tips and in-app notifications
Project Gallery









Challenges & Solutions
Every great project overcomes obstacles. Here's how we tackled the hard problems.
Challenges
- Designing for older adults with very different levels of comfort with a phone
- Serving the elderly member and the family member in one app without mixing up what each can see and do
- Giving families a reliable daily signal without making the parent feel monitored
- Keeping every booking state clear while a person on the care team confirms each visit by hand
Solutions
- Built a design system around large type, large tap targets, plain language and one primary action per screen
- Used role-based navigation and server-side authorisation, so each role sees only its own views
- Reduced the check-in to one tap, with family alerts only for Not Good answers and missed check-ins
- Modelled bookings as explicit states, requested, confirmed, rescheduled, completed or cancelled, shown on every booking
Services used
Build a similar product with these services
Follow the commercial service paths behind this case study.
Related Case Studies
Explore more projects in the same domain.
Impressed by our
craftsmanship?
We bring the same level of dedication and engineering excellence to every project. Let's discuss yours.




