R
Reddy's PizzaCustomer Application
App Flow Blueprint
Structural wireframes for review — they show what sits where on every screen and how the journey connects, without final imagery or colour. Greyscale is intentional: it keeps the conversation on layout and flow. Visual design follows once this structure is signed off.
Image / mediaphoto drops in later
Content blocktext, card, info
Input fieldtyped / tappable
Primary actionred dot = main CTA
Chips / optionsfilters, sizes, tabs
FLOW
The customer journey
Launch to delivery — branches and persistent navigation shown below
1 · Onboarding
Splash↓
Onboarding3 slides↓
Sign in / upphone, Google or email↓
Set addressmap + saved
2 · Menu
Homegreeting · promos⇄
Search→
Product detailcustomise · 11 add-ons
3 · Order
Cartedit · re-customise↓
Deals pop-upskip or add↓
Checkoutdelivery · tip · pay↓
Receiptorder ID
4 · After order
Status trackingpending → delivered↓
Rate & reviewfood · delivery
Reorderfrom history
5 · Maintenance
Store offlineoutside hours / issue↓
Maintenance windowreopens at…
Notify mewhen open
Bottom tabs
HomeMenuFavouritesRe-orderMe
＋ Cart · floating
“Browse” = the full menu / catalogue (renamed from “Menu”). Cart is a floating button, not a tab.
Account hub
Offers & WalletNotificationsAddressesPaymentsSettingsHelp & Support
How to read this document: each screen below is drawn as a simple frame of stacked zones. The label
inside every zone names what goes there. Where the brief calls for several visual treatments — Home,
Product detail and Checkout each have 3 directions in the prototype — only the structure is shown
here, since the layout is shared across directions.