Klini App 2026
The health plan app rebuilt from scratch, with the portal's look and what is happening right on the first screen.
Paula La Rosa, Product & Service Designer and Design Engineer
- Sector
- HealthTech · Health plan
- Role
- Product Design · Design System
- Year
- 2026
Context
The new version of the app for Klini Saúde members. The live app sets the rules and the content; the form is new, in the same system as the Member Portal. More than 450 screens across 11 journeys, from sign-in to lab reports, each with its dark mode pair. The prototype beside it is clickable.
Problem
The live app was a launcher: a grid of shortcuts with no navigation, a grey member card with the plan name cut off and sections with orphan shortcuts. It had a different font, screen size and components than the portal. People who used both felt two different products from the same health plan.
Solution
I rebuilt the foundation from the portal: Inter, the same palette, 48 px buttons and fields and a 390 px screen, the most common device today. The shortcut grid became a five-tab bar, and Home now shows what is happening: today's appointment with the button to join the room, the requests in progress, and shortcuts after that. Each flow takes from the live app only the business rule and the approved copy, never the old component.
What the research showed
How it was done. A heuristic review of the live app, screen by screen, against Nielsen's 10 heuristics, with every issue rated by severity. Alongside it, a journey map of people who use the portal and the app on the same day and a service blueprint from booking to lab report. The review was logged in ProductOS.
Findings
- The problem was orientation, not looks: The shortcut grid did not say where people were or what was happening. Visibility of system status and recognition over recall were the most violated heuristics.
- Two products for the same person: Whoever books on the portal and joins the telehealth call on the phone switches font, buttons and vocabulary mid-journey. The break was in the hand-off between channels, not on one screen.
- What matters today gets lost among shortcuts: Today's appointment and the pending lab report competed for space with rarely used shortcuts. People looked for what was happening and found a menu.
Personas
Marta, 58, Plan holder, looks after the family. Books appointments for herself and her mother, almost always on the phone, and calls the help line when she cannot find something. Needs: See today's appointment and the next step without searching. Gets in the way: Shortcuts with technical names and screens that behave differently on the portal and the app.
Diego, 31, Dependent, uses telehealth. Sorts everything out during work breaks and only opens the app when he needs to. Needs: Join the telehealth room in one tap and get the lab report without calling anyone. Gets in the way: Not knowing whether the request moved or when the report will be ready.
Personas composed from the research. Names and ages are illustrative.
Blueprint: from booked appointment to lab report
- Book. The person: Picks a specialty, day and time. On screen: Open slots and an on-screen confirmation. Backstage: Network schedule lookup and slot hold. Pain point: With no visible confirmation, people call to check.
- Remind. The person: Gets the notice on the day. On screen: Notice with the time and the button to the room. Backstage: Reminder dispatch and eligibility check.
- Join the room. The person: Taps Join the room. On screen: Countdown and video room. Backstage: Room opened with the doctor on duty. Pain point: If the room does not open, there is no clear way out.
- Request. The person: Receives an exam request. On screen: Request in progress, with status. Backstage: Exam authorization by the health plan. Pain point: A stalled status turns into a call to the help line.
- Lab report. The person: Opens the result. On screen: Pending report with a deadline, then available. Backstage: Lab integration and report release.
What was left out
I discarded a purely visual redesign of the shortcut grid: with new icons it would still not say what is happening. I also left NPS out of the service rating, because it measures willingness to recommend the plan, not whether the appointment solved the problem. What stayed is a satisfaction question after the appointment, on a five-point verbal scale.
How to know it worked
- How long it takes from opening the app to joining the telehealth room.
- How many calls to the help line ask about the status of a request or lab report.
- How many people use the portal and the app in the same month without asking for help.
Design decisions
The app inherits the portal
Same font, same palette, same buttons and fields as the Member Portal. Whoever uses the web and the phone finds the same product, and the team maintains a single system.
Home shows what is happening
Instead of the shortcut grid, today's appointment with a countdown and "Join the room", and right below the requests in progress with each status. Shortcuts come later.
2026 components, not inheritance
No bottom sheets: a few actions become a menu anchored to the element, confirmation becomes a centered dialog and critical actions use a hold button. What comes from the old app is rules, never form.
Light and dark from the start
Every screen was designed with its dark mode pair, from the same color variables. Dark mode is not a filter applied at the end.
Results
- More than 450 screens in 11 journeys: Sign-in, health profile, scheduling and telehealth, medical directory, finances, support, health area, dental, my plan and exams and lab reports.
- One system across web and app: The app and the portal share font, color and components, and the development team reads both the same way.
- A clickable prototype: The appointments journey, from the list to the details and the pending lab reports, runs right in Figma.