Mobile · Garnet Health · 2021
Garnet Health Mobile
The hospital's public iOS and Android application, built solo and then handed to a team I led.
How it works
Two native clients over one service layer. The apps hold parity because they share a contract, not because someone remembers to update both.
-
01 · The problem
The hospital had no presence on the device patients actually use. Wayfinding, services, and contact information all required a browser and a search.
-
02 · What I decided
Native on both platforms rather than a wrapper. A hospital app is opened by someone who is stressed, in a car park, on bad signal, and a web view is exactly the wrong thing in that moment.
-
03 · The outcome
Over 5,250 installs, and the codebase that the mobile team I went on to lead was formed around.
What a surveyor, or a hiring panel, should hear.
Constraint
A hospital app is opened by someone stressed, in a car park, on poor signal. That is the worst possible context for a web view, and the strongest argument against the cheap option.
Decision
Native on both platforms over a shared C# service layer, built solo first to prove the shape, then handed to a team I formed and led rather than kept as a personal codebase.
Ownership
Over 5,250 installs, and the mobile practice the hospital now runs on. The handover was the deliverable as much as the app.
- Installs
- 5,250
- Platforms
- Native x2
- Platforms
- iOS · Android