Tru North Tru Life Solutions
2025–2026
As the only designer at a health startup, I designed TruHealth end to end. The platform brings personal and family medical records, symptom tracking and emergency triage together, and I worked closely with the developers to get it built quickly.
Role
Product Designer (sole designer)
Timeline
August 2025 – February 2026
Team
1 designer, 2–3 developers, project lead, owner
Platform
Responsive web app and landing page
Overview
TruHealth brings everything a family tracks about their health into one platform: Apple Watch data, self-logged symptoms, journals and medical records. Patients can spot patterns, check whether they need the ER, and share clear records with any practitioner, even in another country.
The Impact
35+
Health trackers
Brought into one system
50%
Less design time
Templates instead of every screen
30%
Faster prototyping
With Figma AI for handoff
Problem
For users
Health records get lost exactly when they're needed.
Records were scattered across clinics, countries and formats. When a practitioner left, the history often went with them. Meanwhile, ERs handled questions that weren't emergencies, because people had nowhere else to ask.
01
Scattered history
Patients started over with every new provider, and clinics repeated tests because there was no proof of past diagnoses.
02
Emergencies at the wrong door
Without a way to check symptoms first, minor concerns reached the ER alongside real emergencies.
03
Data no one can read quickly
Health data had to be clear enough for families and detailed enough for doctors.
For me
Designing with no documentation and little to learn from.
I joined as the only designer, with a backend already in progress and no documentation or onboarding. Most detailed health software is private, so there was little to study. The owners knew what data they wanted to collect, but not what mattered most on each screen.
Research
I started by learning the existing backend and the product goals. Then I ran structured discovery with the owners, covering vision, primary users, MVP priorities, data sources and brand tone, and reviewed apps like Apple Fitness, Dot Health, Welltory and MyFitnessPal.
Owner discovery
Structured questions on vision, users and MVP.
4 competitors
Apple Fitness, Dot Health, Welltory, MyFitnessPal.
35–40 trackers
Each studied for what it measures and how it relates to others.
Key insights
Families, not individuals. Users range from people in their 20s and 30s to grandparents, and people often log data for someone else.
Owners react to screens, not specs. Priorities only became clear once there was something visual to respond to.
Every tracker is connected. To analyze data properly, I had to understand what each reading means and which conditions it relates to.
Warm, not clinical. The owners wanted the brand's orange, not the blue that most health software uses.
Ideation
I mapped task flows (each action, what the system shows, and each decision point) and built an information architecture for the app, plus a separate one for the very dense settings. Merging redundant sections early reduced the mental load on a stressful topic.
Task flows and information architecture for the app and settings.
01
Key screens before full flows
Designing the important screens first let me explore components and showed the team where the design was heading.
02
One structure for every tracker
A shared layout of graphs over time, date picker, quick overview, filters and input methods, applied tracker by tracker.
03
Triage built for a changing backend
Several versions of the triage flow for different backend possibilities, finalized once the backend was ready.
Evidence, not opinions, settled design debates. Health is personal, and sometimes personal experience outweighed the research, so I presented research-backed visual options that showed how each choice served both users and the business.
Working with the owners
Solutions
Seven decisions: four for patients and doctors, three for the team.
For users
A platform that reads well for patients and doctors alike.
Line charts, bar charts, heat maps, tables and Gantt charts share one visual style, so patients and clinicians can spot abnormal trends in seconds.
Based on the triage process nurses use, symptom selection suggests possible conditions and what to do next, so ERs can focus on real emergencies.
Everything from X-rays to prescriptions lives in one place and goes with the patient to any practitioner, along with a PDF report generated from TruAI.
A separate information architecture groups sharing controls and display options into clear sections, so a dense page stays easy to understand.
For the team
Less time designing, faster handoff.
Together, the team and I decided to fully design only the unique screens, components and flows. Repeated tracker screens became templates that varied only in input fields and chart type, which cut design time in half.
I built reusable components and their variants first, using colours from the logo, the Inter font and Google icons, and checked accessibility throughout. Developers could assemble new screens without waiting on me.
I gave developers code, not just screens.
I used Figma AI to generate interactive states, and Figma Make with Claude to extract HTML/CSS that I reviewed and cleaned up before handoff. That helped developers connect the existing backend to the front end faster, and showed the team that good UX needs as much priority as a strong backend.
Key outcomes
Unified health data
35+ trackers in one consistent, readable system.
Half the design time
Templates and components replaced repetitive screens.
Faster builds
AI-assisted handoff with reviewed code brought design and development closer.
Landing page ready to finish
Left at mid fidelity with 4–5 structures, to complete once the backend confirms features.
Lessons
Being the only designer meant balancing the owners' vision with users' needs while making the developers' work easier. Showing visuals worked better than arguing, and flexible components let the design keep up as the backend changed.
What I’d tell my future self
Build visual anchors early.
Quick wireframes surface hidden priorities faster than written specs.
Advocate with artifacts.
Research-backed visuals win debates that opinions can't.
Design for a moving backend.
Modular components absorb change without a full redesign.
