COLOR SWITCHER

  • yellow
  • green
  • red
  • blue
  • pastel-purple
  • pastel-green
  • pastel-pink
  • pastel-blue
×
Synca+ Glucose AI Hero Image

Synca+ Glucose AI

Turn glucose data into clear actions.

Product Context

Synca+ puts CGM data, notes, and trends in one place.

Patients see now, change, and next step.

Clinicians get a clean view to review and act.

The Problem

  • Data lived in separate apps and portals.
  • Trends were hard to spot quickly.
  • Sharing with providers took many steps.
  • Alerts arrived late or were missed.
  • Mobile flows felt busy and slow.

Role

Fullstack Developer, UI/UX Designer

Timeline / Team / Tools

  • Timeline: Aug 2024 – March 2025
  • Team: 1 CEO, 2 Engineers, 1 Bioengineer
  • Tools: Figma, Miro, Jira, React, FastAPI, TensorFlow, .NET Framework

Goals and Approach

Build a fast, calm app that reduces thinking per screen.

  • Start log in one tap.
  • Time-in-range on home.
  • Share in <30s.

User Journey & Wireframes

Setup → Dashboard → Log → Insights → Report — one clear next step.

Design Components & UI

Colour and typography sheet used across the app.

Colour and type sheet for clear hierarchy.

Final Product

Setup flow showing device pairing and target ranges.

Setup: pair device, set targets, start clean.

Dashboard with current glucose, 24h trend, time-in-range.

Dashboard: current reading, 24h trend, time-in-range.

Daily log screen for recording meals and activity.

Daily Log: record meals, activity, and notes.

Results

  • Setup time: 6–8 → 3–4 minutes.
  • Share report: under 30 seconds.
  • Logging errors: −20–35%.
  • Time-in-range: +4–8% (pilot).
  • Patients act sooner; fewer surprise highs.
  • Clinicians review trends, not raw rows.
  • Fewer “how do I share?” questions.

Reflection

Owning both design and build kept decisions tight. I learned to write the copy first, then shape screens around it. Small, steady releases beat big reveals.

What I'd Do Differently

  • Set up a modular component kit earlier.
  • Bring users into testing sooner.
  • Plan offline logging from day one.