Status
Loading...naman.portfolio / booting
Projects/SafeBite
Health · Product design · 2025

SafeBite

Turning complicated food information into a calmer decision.

Read the story
01 / Project overview

Start with
the context.

SafeBite is a health-information product concept that helps people understand what is in the food they eat. It restructures dense ingredient and dietary information into a clear hierarchy designed for quick understanding without hiding the detail.

Food decisions are often made quickly, while the information supporting them is written for careful reading. Ingredients, allergens and nutrition compete for attention, leaving people to translate unfamiliar language at exactly the moment they need confidence.

My role
Product designer & front-end prototyper
Timeline
Concept project · 2025
Team
Independent project
Methods
Content audit · Comparative review · User-flow mapping · Accessibility review
Tools
Figma · React · Information architecture · Prototyping
02 / Exploration & discovery

Look before
making.

The discovery phase focused on the information itself: what someone needs to know first, what requires explanation and what can wait. Reviewing common food-label patterns exposed a mismatch between regulatory completeness and everyday comprehension.

01

Risk comes first

For people with allergies or restrictions, the first question is not ‘is this healthy?’ but ‘is this safe for me?’ The hierarchy needed to respect that urgency.

02

Plain language builds confidence

Technical names are sometimes necessary, but a short explanation helps people understand why an ingredient matters.

03

More data is not more clarity

Showing every detail at once made the product feel authoritative but harder to use. Progressive disclosure became a core principle.

03 / UX design process

From signals
to a system.

The process moved from abstract questions to increasingly tangible decisions. Each round had one job: expose what was unclear before adding more fidelity.

  1. 01

    Reorder the questions

    I organised the flow around user intent: immediate safety, a simple summary, then supporting detail for people who want to investigate further.

  2. 02

    Design the hierarchy

    Wireframes tested how warnings, explanations and neutral information could coexist without turning the whole interface into an alarm.

  3. 03

    Prototype responsively

    The interface was translated into a React prototype to test content density, interaction states and reading order across screen sizes.

Decision log

Not just what changed—why it changed.

Hierarchy

Answer the urgent question first

Safety-relevant information sits above general product detail, reducing the time needed to reach a decision.

Language

Explain without diagnosing

The product clarifies information but avoids presenting itself as medical advice or replacing professional guidance.

Tone

Calm, not clinical

A restrained visual system communicates seriousness without adding fear to an already uncertain moment.

04 / Final design

The idea,
made tangible.

The final design uses a layered information model: a concise top-level answer, plain-language context and optional deeper detail. The experience is designed to support a decision, not reward endless scrolling.

Safety at a glance

The most consequential information receives the clearest position and strongest visual distinction.

Plain-language context

Unfamiliar terms are paired with concise explanations that preserve accuracy without assuming expertise.

Progressive detail

Additional information stays accessible but does not compete with the immediate decision.

Accessible structure

Clear labels, semantic order and strong contrast support scanning and assistive technology.

05 / Impact

What moved
forward.

SafeBite remains a concept prototype, so I frame impact through the usability improvements designed into the information model rather than invented conversion numbers.

  • 01Reduced a dense information problem to a three-level reading hierarchy.
  • 02Made accessibility and health literacy part of the product structure, not a final check.
  • 03Produced a responsive prototype that can support future usability testing.
06 / Learnings

Keep the lesson.
Lose the ego.

01Health information needs both clarity and humility: an interface should explain what it knows and be honest about what it cannot decide for someone.

02Visual calm is functional when users are already carrying uncertainty.

03The next phase should involve participants with different dietary needs and include expert review of the content model.

Useful information should lower the temperature of a decision.
Next case studySoftly