Too many places to figure out how to order.
Pickup, local delivery, and shipping each introduced different questions, timing, and expectations.
Consumer commerce · Native iOS concept
Bizzy Bakery
Turning a fragmented ordering process into one clear mobile flow.
Bizzy Bakery had strong product demand, but ordering depended on several different channels and fulfillment methods. I designed a mobile experience that lets customers browse, build an order, and request pickup, local delivery, or nationwide shipping without forcing the business into an operational model it was not ready to support.
The business problem
Demand was growing. The ordering experience had not caught up.
Customers could discover the bakery through social channels, delivery platforms, direct messages, and word of mouth, but the path from craving a product to placing the right kind of order was fragmented.
Every order still needed operational judgment.
Availability, timing, local delivery details, and nationwide shipping costs could not always be guaranteed instantly.
A standard ecommerce checkout was the wrong first move.
The MVP needed to organize demand without promising automation the business could not reliably fulfill yet.
Product strategy
Design the experience around confirmation, not assumption.
Instead of forcing Bizzy Bakery into an instant checkout model, the app treats ordering as a structured request. Customers make their choices first, then the bakery confirms the details that still require human judgment before payment.
01BrowseDiscover flavors and products
02BuildChoose size and quantity
03RequestSelect fulfillment details
04ConfirmBakery verifies timing and cost
01 · Discovery
Lead with the product customers already crave.
The menu experience is visual and direct. A featured product, search, category filters, and product imagery make discovery feel closer to browsing a bakery counter than navigating a utility app.
Menu home
Brand personality without losing clarity.
Bizzy Bakery already had a playful, high-energy identity. The interface keeps the pink, cream, and chocolate palette while giving the experience stronger hierarchy, navigation, and product structure.
- Featured product for immediate discovery
- Search for customers who know what they want
- Category filters for faster browsing
- Persistent access to Menu, Cart, and Order
02 · Product selection
Make product decisions feel simple and appetizing.
The product detail view keeps the food image dominant, then narrows the decision to the few things that matter: what it is, which size the customer wants, how many, and the price.
01
Visual first
Large photography carries the emotional part of the purchase so copy can stay short.
02
Few choices at a time
Size selection is grouped into clear cards instead of a dense configuration form.
03
Persistent action
The add-to-cart action remains visible near the bottom so the customer always knows the next step.
03 · Empty state
An empty cart should still help the customer move.
Instead of treating an empty cart like an error, the screen reinforces the product promise and gives one obvious recovery action: browse flavors.
The branded illustration and direct CTA keep the state useful without adding complexity.
04 · Fulfillment
One order flow, three different operational realities.
Pickup, local delivery, and nationwide shipping share the same entry point but reveal different information as the customer selects a method.
Choose a date and available pickup time.
Collect the request before confirming delivery details.
Set expectations before payment.
Key design decision
Do not automate what the business still needs to verify.
The most important UX decision was keeping the final step as a request rather than a guaranteed transaction.
That protects both sides. Customers understand that fulfillment details are confirmed first, while the bakery keeps control over timing, availability, delivery logistics, and shipping cost.
This made the MVP useful immediately without requiring a full inventory, logistics, payment, and shipping automation stack on day one.
Visual system
Playful enough for dessert. Structured enough for commerce.
The visual language uses the bakery's existing personality as the emotional layer, then adds a cleaner interaction system underneath it.
Brand-led palette
Hot pink carries primary actions while cream and blush keep the product warm and food-forward.
Aa
Friendly hierarchy
Bold rounded display type gives the app personality, while simpler supporting copy keeps long forms readable.
MenuCartOrder
Persistent navigation
Three core destinations keep the information architecture understandable without a deep menu structure.
AI-assisted build process
From product strategy to working iOS experience with AI in the loop.
Bizzy Bakery was heavily AI-assisted throughout the process. I used AI to accelerate research, product thinking, interface exploration, implementation, debugging, and QA while keeping product decisions and experience quality under my direction.
ChatGPT
Used for ideation, business-model thinking, MVP scoping, fulfillment strategy, UX flows, microcopy, edge cases, and design critique.
Figma
Used to shape the product experience, visual language, ordering flow, component patterns, and interaction hierarchy.
Codex
Used heavily to translate product requirements into implementation, iterate on native iOS features, debug behavior, and refine the experience.
VS Code
Used to work directly with the codebase, review changes, manage implementation details, and validate fixes across iterations.
Xcode + Simulator
Used to test navigation, fulfillment states, visual fidelity, interaction behavior, and the actual end-to-end ordering experience.
Research + strategy
→
UX + visual design
→
AI-assisted implementation
→
Simulator QA
→
Iteration
MVP outcome
A realistic path from social demand to structured orders.
The concept creates a clear customer journey without pretending the bakery operates like a large ecommerce company.
- Unified product discovery and ordering in one mobile experience
- Supported pickup, local delivery, and nationwide shipping
- Reduced ambiguity around what happens before payment
- Preserved owner control over fulfillment decisions
- Used an AI-assisted design and development workflow to move from concept into a functioning iOS experience
- Created a foundation that can later support payments, loyalty, logistics integrations, and admin tools