14 / 19 · Heal at home

Portea

Portea brings doctors, nurses, physiotherapists and rented equipment to the patient's home. I designed the Android app around one familiar object, the hospital registration card, from booking and chat to visit tracking and family records.

Role
Product designer
Client
Portea
Industry
Healthcare & life sciences
Year
2015
Work
Product design, UI design, Interaction design

A daughter in another city needs a physiotherapist to visit her father. Portea brings that kind of care home: doctors, physiotherapists, nurses, diagnostics, medicines, trained attendants and rented medical equipment, delivered to the patient's door.

Most of the people opening the app are patients, or relatives booking for them, often while unwell or worried. A long, complicated journey would push them back to the phone line, and the business still needed the app to sell services.

What would make booking care at home feel as familiar as checking in at a hospital desk?

I built the whole app on one idea: the patient registration card that hospitals across India already use. Services, equipment, bookings, subscriptions, health records and profiles all appear as cards, so every screen reads the same way. Steps are kept to a minimum, floating actions keep booking in reach, and chat lets a family member ask a clinician for free before they buy.

My role

Product designer. Designed the Android app experience: the card-based concept, home and navigation, the services and equipment catalogues, the four-step booking wizard, chat, order tracking, health records and family profiles.

What made it hard

  • Patients first

    The audience is people seeking treatment, so the experience had to be minimal and simple, with as few steps as possible.

  • Many services, one pattern

    Doctor visits, nursing, physiotherapy, equipment rental and subscriptions each have different details. One card pattern had to hold all of them.

  • Booking on behalf of others

    Care is often arranged by a son or daughter. Profiles, chat and booking had to work for someone acting for a parent.

  • Design that sells

    The app had to drive bookings. Floating calls to action and chat-led consultations were designed to turn questions into orders.

Questions we asked

  1. What does a patient already recognise from a hospital visit?
  2. How many steps can a booking take before people give up and call?
  3. How do we show who is coming to the house, and when?
  4. How does a daughter book physiotherapy for her father from another city?
01

The registration card

The home screen is a gateway to every part of the app, built to Google's Material Design guidelines. A greeting and search sit over a photo carousel, a chat card invites questions, and services follow as cards. A yellow floating button opens chat, call, payment and camera. Swipe right for the sidebar: recently viewed, orders, subscriptions, health records, payments and wallet.

The registration card

The sidebar slides over the home screen and gathers orders, records and payments in one list.

02

Services and equipment

A catalogue of photo cards presents doctor consultations, nurses and physiotherapy at home, with search. Detail screens leave breathing room for price, description and key features, with a price list for single visits and packages. The same pattern lists rentable equipment such as ICU beds, ECG machines and monitors, priced per day, with a date-range picker.

Services and equipment

Services and rentable equipment share one photo-card pattern, from catalogue to detail.

03

A four-step booking

The booking wizard has four steps. Date and time slots are grouped into morning, afternoon and evening. The summary links the appointment, clinician, service, price and time as connected blocks, like pages in a file, with the choice to pay now or later.

A four-step booking
A four-step booking

The wizard starts with time slots grouped by part of the day and ends on a linked summary.

04

Ask before you book

Consultation by chat is free. A user can create a profile for a relative or friend and ask on their behalf, and a care coordinator can bring a doctor into the conversation. The chat was also meant to lead people towards booking.

Ask before you book

Each chat shows who it is for, so a relative can ask on a parent's behalf.

05

Orders, tracking and records

Subscriptions stack as a deck of cards with a status trail from session to delivery. A live map shows how far away the clinician is, who is coming, and buttons to call or chat. Health cards keep each episode, with tabs for case file, vitals and treatment.

Orders, tracking and records

A live map shows who is coming and when; subscriptions and health cards follow the same card form.

06

Care for the family

The profile is one more card, with counts of health records, appointments and subscriptions. Add Family finds existing Portea members by mobile number and sets the relationship, so one person can book services for another.

Care for the family
Care for the family

Add Family matches an existing member by mobile number and sets the relationship.

In motion

Outcomes

  • 1card pattern across the whole app
  • 4steps in the booking wizard
  • 8flows designed, from catalogue to family profiles

What I took away

  • Borrow the object people already trust. A registration card made a new app feel familiar.
  • One pattern, used everywhere, does more for simplicity than any single clever screen.
  • In family healthcare, the user is often not the patient. Design for the person booking on someone's behalf.
Product designer
Preetham Lawrence
Have a hard problem worth solving?

Let's solve it together.

preetham.lawrence@icloud.com
+41 76 740 46 30Phone
LinkedIn↗ Writing on Medium↗

Design leader based in Zürich, Switzerland. Open to leadership roles and selected collaborations.

© 2026 Preetham LawrenceIndex