Loading

0

Role

Fullstack Developer,
UI/UX Designer

Timeline

Aug 2024 –
March 2025

Skills
UI/UX Design User Testing Full-Stack Development ML Integration Product Strategy
Team
1 CEO 2 Engineers 1 Bioengineer
Tools
Figma, Miro, Jira React, FastAPI TensorFlow .NET Framework

Synca+, CGM Mobile Companion for Patients and Providers

PRODUCT CONTEXT

I designed and developed Synca+ as a full-stack CGM companion app with the goal of transforming scattered glucose data into a unified, actionable experience. The project included crafting an interface where patients, clinicians, and insurers could engage with real-time insights, prediction, and device management in one coherent flow. The product emerged from a clear gap: raw data alone wasn't enough. Users needed clarity, connection, and context.

THE PROBLEM

Diabetes management today suffers from fractured workflows: CGM apps track glucose, doctors manage care elsewhere, and insurers sit at a distance. Patients are left navigating multiple systems that don't talk to each other. Through direct research and prototyping, I saw how this fragmentation created confusion, delayed care, and led to preventable risk. My challenge was to rethink the experience from the ground up, designing a system where each role could act earlier, communicate faster, and trust what they see.

User Journey & Wireframes

Mapping the complete user experience from initial setup to ongoing glucose management

User Journey

Interactive flow mapping the complete user experience from initial setup to ongoing glucose management through AI-powered insights.

1

Initial Setup

Profile & device pairing

2 min
Welcome to Synca+.
Name
Age
Email
Device ID
Get Started
2

Daily Logging

Quick glucose tracking

30 sec
Glucose Level
142 mg/dL
Target Range
8.2% A1C Est.
Add Meal
Add Reading
Log Activity
3

AI Analysis

Pattern recognition

Real-time

Content Restricted

Content removed due to NDA. Please contact me for additional inquiry.

6

Doctor Sharing

Healthcare integration

Secure
5

Health Reports

Progress tracking

Weekly
7-Day Summary
84% In Range
142 Avg. Level
2.1% Improvement
4

Insights & Alerts

Smart recommendations

Proactive
⚠️
Higher levels after lunch
Morning levels stable
Recommended Action

Consider smaller lunch portions or increase activity

I conducted iterative research

To design Synca+, I led a recursive process of mapping user journeys, creating wireframes, and organizing the information architecture. I consistently moved between patient needs, clinical workflows, and device limitations. Each round revealed gaps in clarity or flow, requiring trade-offs between simplicity and clinical thoroughness. This close feedback loop was essential for creating an experience that could work for different roles without overwhelming any single user.

Interactive Wireframe

Use this prototype!

Experience my design process as a user by exploring the flow in the app in real-time.

Goals and Approach

Sleep Icon

My goal with Synca+ was to design a unified, patient-centered interface that could manage complex glucose data, predictive AI outputs, and multi-role collaboration across clinical, administrative, and patient-facing environments. To accomplish this, I followed a recursive design process that combined journey mapping, wireframing, stakeholder workshops, and iterative A/B testing. This approach allowed us to validate layout decisions, refine interaction patterns, and ensure alignment between clinical requirements and user behavior. I placed a strong emphasis on trust-building UI elements, adaptive data visualization, and interface modularity. The result was a system that could scale across user types without sacrificing clarity, usability, or compliance with healthcare standards.

Design Components & UI

Comprehensive design system and component library built for consistency and scalability

Synca+ UI Components and Design System

The Synca+ design system features a comprehensive component library with consistent typography, color schemes, and interactive elements. Each component was designed with accessibility and user experience in mind, ensuring seamless integration across all app screens and maintaining visual consistency throughout the diabetes management workflow.

Final Product

Some screenshots of Synca+ in beta test

Results

8 Months Product Duration
95% User Satisfaction Rate
76% Improved Glucose Management
3x Increase in Clinician Response Speed
85% Prediction Accuracy Achieved by ML Engine
$3.4M Dollars Gained in Funding

Reflection

Taking on both full-stack development and design for Synca+ was one of the most challenging projects I've worked on. Balancing technical execution with product strategy pushed me out of my comfort zone. It taught me how to move faster, make clearer decisions, and stay closely connected with engineers, stakeholders, and users. That kind of pressure turned out to be valuable. It changed how I approach problems, giving me more flexibility, better context, and a stronger sense of how every part of a system fits together.


It also forced me to be intentional with every decision. There was no room for vague handoffs or guesswork. Whether I was designing a predictive graph, mapping API responses, or walking a clinician through a prototype, I had to own the outcome from start to finish. That level of responsibility sharpened both my technical skills and my product instinct. It reminded me that great products don't come from choosing between design and engineering; they come from knowing how to navigate both.

What I'd Do Differently

If I were to revisit Synca+, I would invest earlier in creating a more modular design system and component library. Since I was managing both design and development, some UI decisions were made on the fly, especially when facing engineering deadlines. Setting up reusable patterns from the start would have saved time and created more consistency as the product evolved. I would also involve users in the feedback process sooner, not just for usability but for validating concepts. This would help challenge assumptions before committing to key flows. The project went well, but with stronger support and earlier testing, I could have scaled faster with fewer iterations.