Dietary Supplement Protocol App
- Project title
- Uzenda
- Target
- Self-initiated project
- Status
- shipped
- Year
- 2026
- Role
- Product designer, full-stack, DevOps
- Skill
- UX/UI, product strategy, data architecture, IA integration
Overview
How do you know if your health protocol is actually working?
I was running a personal supplement protocol with no real visibility into what I was taking, when I was taking it, what I was spending, or whether any of it was actually correlated with how I felt. The information existed, but it was fragmented: supplements in different places, intake remembered manually, stock checked occasionally, and subjective feelings disconnected from the protocol. In less than 24 hours on a weekend I built Uzenda to turn that fragmented routine into a structured system.
OPPORTUNITY
Uzenda can evolve from a tracking tool into a private health commerce layer. When a product is about to run out, the user can reorder it directly from the protocol rather than starting a new search. The e-commerce experience therefore becomes a consequence of the user's existing health routine rather than a separate shopping destination.
SOLUTION
Uzenda combines health protocol management, tracking, personal insights and replenishment into one system.
PERFORMANCE
Athletes and performance-oriented users tracking supplementation, recovery, sleep and energy
BIO-HACKING
Users experimenting with protocols and interested in measuring relationships between interventions and personal signals
AESTHETIC CARE
Protocols around skincare, haircare and other long-term routines
PREVENTIVE HEALTH
People building structured daily health routines
SPECIFIC LIFE JOURNEYS
Hormonal journeys, restrictive diets and other situations requiring structured supplementation
SENIORS
Users managing multiple products and recurring intake schedules
KEY FEATURES
PROTOCOL
The protocol is the core object of Uzenda. Instead of managing individual supplements independently, users create a structured protocol with a defined duration, schedule and set of products. Each protocol becomes a living dashboard: - duration - remaining days - supplements - intake - stock - budget - insights
PROTOCOL
STOCK
Every protocol creates a predictable consumption cycle. As products are consumed, Uzenda estimates remaining stock and anticipates when a supplement will run out. The future experience: Running low → Reorder → Continue protocol without leaving the application. This creates the foundation for Uzenda's future private health-commerce layer.
SCAN & TRACK
Adding a supplement should not feel like entering data into a database. Uzenda uses scanning as the primary entry point. Scan the product → identify it → add it to the protocol. Manual entry remains available when scanning is not appropriate. The same system then tracks daily consumption and missed doses.
INSIGHTS
Tracking intake alone is not enough. Uzenda connects protocol data with subjective lifestyle signals such as: - energy - mood - sleep - concentration - digestion - nutrition The goal is to transform raw tracking into meaningful observations over time.
REPLENISHMENT
The protocol is the core object of Uzenda. Instead of managing individual supplements independently, users create a structured protocol with a defined duration, schedule and set of products. Each protocol becomes a living dashboard: - duration - remaining days - supplements - intake - stock - budget - insights
CONSTRAINTS
01 — Technical
- PWA constraints
- Mobile-first interaction
- Barcode / product scanning
- Data synchronisation
- Notifications
- AI-generated reports
- Correlation processing
02 — Data
- Health-related data requires careful handling.
- Personal data must be structured with privacy in mind.
- Correlations must not be presented as medical causation.
- User-entered data can be incomplete or subjective.
03 — Business
- AI inference and compute costs
- Product database maintenance
- E-commerce infrastructure
- Payment and logistics
- Potential regulatory constraints
04 — User
- Tracking must remain low-friction.
- Too many inputs create abandonment.
- Health information can quickly become overwhelming.
- The product must avoid pretending to replace medical advice.
WHAT I LEARNED
- Fast execution.
- How to transform a personal pain point into a structured product system.
- How information architecture becomes critical when several types of data need to coexist.
- How to design around a data model rather than isolated screens.
- How to move from product concept to functional PWA extremely quickly.
- Improving my full-stack development and DevOps workflow.
- Designing AI features around useful outputs rather than AI as a standalone feature.
WHAT'S NEXT
- Expand the protocol engine beyond supplements
- Product database / catalogue
- Barcode and product recognition
- AI-generated weekly / monthly reports
- More lifestyle signals
- Protocol adherence analytics
- Stock prediction
- Private replenishment marketplace
- Direct supplement reordering
- Brand / retailer partnerships