When the ice cream is perfect but the digital experience isn’t — a case study in closing the gap between a great product and a broken customer journey.
The World Before
Picture a hot afternoon. You’re craving something cold, something real — not artificial flavouring packed in plastic. You want the actual taste of a mango, a strawberry, a passion fruit. You pull out your phone to find a FruitIce outlet. The outlet page on Google Maps hasn’t been updated since 2023. You call — no answer. You drive there anyway. It’s closed. This is the experience FruitIce’s product deserves to never have again.
What is FruitIce?
A mobile app concept tackling five real friction points — no stock visibility, no store finder, no loyalty tracking, no launch alerts, no real-time hours — between a great product and the customers who want it.
FruitIce is a mobile app concept for a real fruit-based ice cream brand. The brief was straightforward on the surface: design a digital experience for a physical product. The complexity was underneath — the brand had a loyal customer base but zero digital infrastructure. No app. No live stock data. No loyalty tracking. Customers were discovering closures on arrival and missing limited-edition launches entirely.
The design approach was constraint-first. Before any wireframe, I mapped the exact moments where customers abandoned the brand — not because the ice cream wasn’t good, but because finding it was too hard. Every screen in this app is a direct response to one of those moments. Nothing was added for visual interest alone.
The outcome is a six-screen concept covering the full customer journey: flavor discovery with live stock status, GPS store locator, real-time hours and closures, customizable order flow, loyalty rewards dashboard, and a push notification system for limited editions. The Figma prototype is fully interactive across all five primary user flows.
“I drove to three FruitIce shops last Saturday. Two were closed. One had run out of my flavor. There was no way to know in advance — no app, no status, no update. I ended up at a different brand instead.”
Five Things That Were Broken
FruitIce’s ice cream sells itself. The flavours are exceptional, the ingredients are real, the product has genuine word-of-mouth traction. But every conversation with a customer — in user interviews, on social media, in app store reviews for comparable brands — surfaced the same pattern: the physical product was winning, and the digital experience was losing the customers it worked so hard to earn. There were five specific moments where that loss happened.
Five things blocking joy
Identified through a competitive audit of four food apps (Swiggy, Zomato, Amul, and Baskin-Robbins India) and four informal conversations with regular ice cream buyers. These are not invented personas — they are five consistently recurring moments of drop-off.
FruitIce’s product is exceptional. The experience gap was entirely digital. No customer was leaving because the ice cream wasn’t good enough — they were leaving because they couldn’t find it, couldn’t check it, couldn’t track it. The design challenge: make the physical delight accessible before the first scoop.
Designing the Answer
Before a single wireframe was drawn, each of the five pain points was converted into a design question. Not “what should the stock page look like?” but “at what moment in the customer journey does stock information need to appear, and how little effort should it require to access it?” Every solution in FruitIce starts with a question, not a feature.
Five answers to five problems
Each solution maps exactly to a pain point — showing what was tried first and why this approach won
The Design Process
Great apps don’t come from one great idea — they come from a disciplined process. For FruitIce, that meant starting with understanding before ever opening Figma. The design had to earn its colour before it could wear it.
From insight to screen
Four phases, each building on the last — research informing architecture, architecture enabling design, design proving itself in testing
Competitive audit of four apps (Swiggy, Zomato, Amul, Baskin-Robbins India) revealed one consistent gap: none of them surface real-time stock status on the flavor browse screen. All four bury it behind a product detail page — or don’t show it at all. This became FruitIce’s primary differentiator. User journey mapping showed the decision to visit a store happens before leaving home, not at the store — which moved the GPS locator from a utility feature to a navigation-level priority.
Information architecture centred around one question: what does a user need to know before they leave the house? That answer shaped the entire hierarchy — stock status and store finder are first-class navigation items, not buried in settings. The loyalty program logic required the most iteration here: mapping every moment where a user might want to see their points balance revealed that the program was only useful if visible at the moment of decision, not just the moment of redemption.
Wireframes went through three rounds before reaching high-fidelity. The first round used a dark background with light cards — pulled back because it felt clinical for a food brand. Second round used full-bleed fruit photography backgrounds — too heavy, slowed navigation. Final direction: dark background as a canvas, fruit photography as the hero of each card, brand cyan as the primary interactive signal. Energetic without competing with the food imagery.
Full interactive prototype tested across all five primary user flows. Two flows needed significant changes: the customization screen originally required scrolling to reach the add-to-cart button — reorganised to keep the action always in thumb reach. The loyalty redemption flow initially required a separate confirmation step at checkout — removed after it became clear the extra step created hesitation at the moment when automatic redemption was the entire point.
The Screens
Each screen in FruitIce tells a specific part of the story. From the first impression that makes you want to eat through the screen, to the GPS screen that turns finding ice cream into an adventure. Design that makes the product feel even better than it already is.
Six features, one craving
Each feature solves exactly one problem — together they create an experience worth coming back for
Screens that make you hungry
Six key screens — each one annotated with the problem it solves, the key decision made, and what changed in iteration

The first impression — bold, colorful, immediate. The brand’s joy is communicated before a single tap.

Vivid flavor cards with real fruit imagery, descriptions, and live stock status. Designed to make you want everything.

GPS map with nearest outlets, real-time open/closed status, hours, and one-tap directions. Finding FruitIce is now effortless.

Touch-friendly animated menu with customization, add-ons, and a seamless checkout. The fun part — drag, tap, select.

Full rewards dashboard — points balance, available treats, redemption history. No staff needed, no confusion, just treats.

A dedicated space where users control preferences, saved items, notifications, and account settings for a seamless personalized journey.
Choices that define the app
Every decision has a reason — and every reason includes what was considered and rejected
Colour, Type & Motion
Every visual choice in FruitIce is intentional — the design language that makes the brand feel as fresh on screen as the ice cream does in your hand
Summer.
before the first scoop.”
SCENE 02 — FLAVOUR
₹180 · Mango Sorbet · In Stock
XS
SM
MD
LG
XL
2XL
Section
Hero
Sharp
Card
Icon
Feature
Tag
Avatar
If FruitIce went live tomorrow
Design targets and informed projections — each figure cites a comparable benchmark or is explicitly labelled as a hypothesis
“I open the app. Mango Sorbet is in stock at the outlet 800m from me. It closes in 2 hours. My loyalty points cover half the order. I’m already on my way.“
What I Learned
Every project teaches something that no brief can predict. FruitIce taught me that brand personality is not decoration — it is the product. The design had to taste like the ice cream before anyone took a bite.
What this project taught me
Designing FruitIce changed how I think about brand, playfulness, and the relationship between UI and physical product
Let’s work together.
FruitIce was a constraint-first project. No brief, no client, no pre-existing research base — just five real failure moments and a question: what would an app have to do to eliminate each one? If you work on problems that need that kind of thinking — starting with the failure before designing the solution — let’s talk.