overview
role: product designer
team: client (developer)
platform: React Native mobile app
GoomY: simplifying core recipe flows and building a distinctive mobile experience in four weeks
GoomY is a French mobile recipe app that helps people save recipes from social media, organize them into collections, and quickly find what they want to cook
what I worked on
app redesign
core flow improvements
design system development
results
redesigned 86 screens and states across onboarding, core app and recipe flows
built 70+ components, 450+ design tokens and styles
delivered the redesign in four weeks
challenge
GoomY was already a working app, but the interface lacked a consistent visual language and did not express the playful, food-focused brand identity which was aimed by the client
The redesign also needed to simplify core flows without rebuilding the product logic. I had four weeks to redesign the app and prepare a system the client could implement in React Native
the navigation patterns and component was not consistent
recipe covers did not look tasty in the layout
controls looked too generic for a recipe app
active controls messed up with inactive tags
recipe covers did not look tasty in the layout
the navigation patterns and component was not consistent
active controls messed up with inactive tags
controls looked too generic for a recipe app
process
Conducted screenshot audit, then aligned priorities and constraints with the client
Explored bold, colorful and food-first visual directions and approved the best
Validated the direction on key screens and approved the concept before rollout
Redesigned onboarding and the main product flows, simplifying navigation where needed
Expanded the approved UI across 86 final screens and product states
Built 70+ components and a 450+ token system, with specs for React Native implementation
review modal appears before users get value
“Get Started” does not begin the onboarding flow
onboarding underplays user pains and gains
trial terms and CTA behavior are unclear
the product demo is disconnected from activation
activation ends before the first saved-recipe aha moment
page and folder navigation are overly complex
adding recipes is hard to discover
views, controls and modals feel inconsistent
some prioritised audit tickets where more saturated = more critical
- Onboarding
- Product Value
Value before commitment
Three focused screens introduce saving social recipes, planning meals and building collections before permissions and the trial decision
- Monetization
- Activation
From trial to first saved recipe
Plans and benefits stay accessible through a sticky CTA; activation continues through hold-to-commit, recipe selection and the first save
- Recipes
- Cooking Mode
A recipe view built for cooking
Users adjust servings, check off ingredients or open the original source, then switch to step-by-step cooking with persistent progress
Full Product Rollout
86 screens
I extended the visual direction across onboarding and core screens covering the flows and states for production
app design system
token architecture
450+ tokens connected Primitive, Semantic and Component level
handoff
Specs, DESIGN.md and tokens enabled accurate React Native implementation
component library
72 component families covered core patterns, states and recipe-specific UI
