top of page

myAster

A smart application that reshapes the perception of healthcare for the integrated service era
Aster.png

Client

UAE

Industry

Healthcare

Introduction

myAster was designed to bring healthcare services together in one digital ecosystem, including Doctor Consultation, Pharmacy, Homecare and Lab Tests.​

Timeline

2.5 years

Designing a unified healthcare Super App

Bring multiple healthcare services into one Super App. A unified experience for the users- from doctor consultation to pharmacy and keeping there health records safe in one app.

Product Strategy & IA​

🧩 Challenge

Each service had its own user journeys, functionality and navigation requirements. While this allowed individual services to support their specific needs, it introduced a broader product design challenge: how could we make multiple services feel like one cohesive Super App without compromising the usability of individual experiences?​

THE DESIGN CHALLENGE

How might we make Aster feel like one connected healthcare ecosystem while preserving the task-specific navigation of each service?

🌟 Identified and Analysed the Problem

The business was organized by services. The customer journey wasn't.

The business context was to bring multiple healthcare services into a unified application. My design challenge was to translate that ambition into an understandable navigation model.
Looking at the services individually, their navigation could be logical. However, looking at them as one product raised a different question: how would users maintain a consistent understanding of where they were and how to move between services?​
​
This led me to identify a potential experience gap:
image.png
Individual experiences

​Consultation, Pharmacy, Homecare and Lab Tests each had distinct workflows and navigation needs.

One healthcare experience

Users needed a consistent way to access services and manage their healthcare needs across the app.

image.png
The product needed a consistent ecosystem-level navigation model, not just well-structured navigation within individual services.

I reframed the problem from “How should each service be navigated?” to:

“How can we make the services easy to discover and access across Aster, while allowing each service to retain the navigation it needs?”

Information Architecture

image.png

🔍︎ Explored Alternate Solutions

I explored different navigation models to understand the trade-offs between service discoverability, global consistency, scalability and the depth required by individual healthcare journeys.

image.png

Option 1 · Rejected

Put every service in the bottom navigation

Concept: Use the persistent bottom bar for Consultation, Pharmacy, Homecare, Labs and other services

Why it was considered: Makes major services directly accessible.

Why I moved away from it: It mixes service discovery with persistent user-management needs, such as Records and Account. As the ecosystem grows, the bottom navigation could become crowded and harder to prioritize.

image.png

Option 2 · Rejected

Hide services inside a menu

Concept: Put all healthcare verticals inside a hamburger menu or service directory.

Why it was considered: Keeps the main interface visually clean and can accommodate more destinations.

Why I moved away from it: Important services become less visible. Users may need to open a menu before discovering what Aster offers, adding an extra step to service discovery.

image.png

Option 3 · Rejected

One common bottom navigation for every service

Concept: It assumes users have the same mental model across all services.

Why I moved away from it: It assumes users have the same mental model across all services.

It also creates problems:

  • Pharmacy needs commerce-oriented navigation.

  • Consultation needs healthcare/appointment-oriented navigation.

  • Homecare needs service-discovery/booking navigation.

  • Important service-specific destinations get pushed out.

  • The navigation becomes generic rather than task-oriented.

🎯 The Decision: A hybrid navigation model

One ecosystem. Two navigation layers. Distinct responsibilities.

I chose a hybrid model that separates healthcare service discovery from persistent user-level navigation.

 

Instead of forcing every service into one navigation structure, I gave each layer a clear responsibility.

Layer 1 · Service Level

Explore Aster Services

image.png

Layer 2 · Bottom Navigation

Manage Service Level Needs

image.png
image.png
image.png
image.png

Success Metrics

01

Navigation effectiveness

Did users understand where to go?
  • How quickly users can identify and enter the appropriate service.
  • Whether users can successfully reach the intended service without assistance.
  • How often users move backward or return to previous screens because they can't identify the correct destination.
  • Wrong destinations
  • Navigation-related support queries

02

Cross-service behaviour

Did the ecosystem become more connected?
  • Consultation → Pharmacy
  • Consultation → Lab
  • Consultation → Homecare
  • Users engaging with 2+ services
  • Repeat cross-service usage

Business Impact

03

Did better discoverability translate into behaviour?
  • Did better service discovery lead to more completed service transactions?
  • What percentage of customers who use one service subsequently transact with another?
  • Does easier movement between services increase repeat engagement?
  • Do customers using multiple Aster services have higher long-term engagement/value?

Note:

These were the success metrics I proposed to validate the navigation strategy.

Book Lab Tests

Book lab test as prescribed by doctor. Considering that you recently visited a doctor who recommended that you undergo several laboratory tests. Instead of contacting the clinic directly, you decide to use a mobile app to manage the entire process.
Designed the end-to-end experience, from discovering and selecting the required tests to successfully completing the booking.

🤔 User Problem

Doctor recommends 5 tests. User opens pharmacy/healthcare app. User has to manually search each test.

🧩 Challenge

Finding multiple doctor-recommended tests manually is time-consuming and error-prone. 

Users don't necessarily know:

  • exact test names

  • whether two tests are duplicates

  • whether tests can be booked together

  • preparation requirements

🌟 Insight

Users know "my doctor prescribed these tests" better than they know the exact names of the tests.

🎯 Design Opportunity

Let the prescription become the starting point of the journey.

How should users add tests?

Option 1

🔍︎

Search Manually

✅ Easy to build

❌ High cognitive load

Option 2

📂

Browse by category

✅ Discoverable

❌ Doesn't match doctor's prescription language

Option 3

⬆️

Upload Prescription

✅ Lowest user effort

❌ Requires OCR + validation

✅ Matches user's mental model

🏆

🥇 Decision: Upload Prescription

Because it reduced the number of decisions users needed to make.

Information Architecture

IA- Rx.png
Home-Upload Rx.png

Upload Prescription

Upload Rx.png

Scan Prescription

Prescription Extracted

• Editable extraction

OCR can make mistakes → users can verify and correct results.

​

• Grouped tests

Tests are grouped to reduce scanning effort.

​

• Preparation

Important preparation requirements are surfaced before booking.

Overview.png

Confirmation

Confirmation.png

Schedule Collection

Schedule.png

Review Details

Checkout.png
bottom of page