DEALS
in use.
Interfaces, states and developer tooling are shown as evidence of product behavior rather than a technology logo collection.
05Deals
A coupon and cashback product for discovery, saved offers, search, notifications, offline use and Arabic/English localization.
ProductFlutter / Dart
StateBLoC / Cubit
ServicesFirebase
ExperienceOffline / RTL
Human
scale.
Deals
Featured todayOffers worth opening.Explore deal →
00 / 09Product
Chapter 00
05 / DEALS
05 / DEALS
Product
The product world changes because the user context changes.
Deals shifts the visual rhythm from enterprise density to human-scale mobile interaction. It is built for quick discovery, saving and return visits.
Different surface. Same responsibility.
The product world changes because the user context changes.
The product world changes because the user context changes.
Chapter 01
05 / DEALS
05 / DEALS
Discovery
Consumer flows reward clarity.
Store and offer discovery need to move quickly from browsing to a useful action without burying value under interface noise.
DEALS
Structure
you can inspect.
The visual connects what a user touches to the decisions underneath it.
DEChapter 02
05 / DEALS
05 / DEALS
Search / bookmarks
Persistence turns discovery into a relationship.
Search and saved state make the product useful across sessions instead of only during one browsing moment.
DEALS
in use.
Interfaces, states and developer tooling are shown as evidence of product behavior rather than a technology logo collection.
05Structure
you can inspect.
The visual connects what a user touches to the decisions underneath it.
DEChapter 03
05 / DEALS
05 / DEALS
Offer experience
The device is the primary canvas.
Offer detail, CTA state and store context need to stay legible on small screens where every element competes for space.
01
Make boundaries visible
Prefer explicit modules, state and contracts over hidden magic.
02
Keep workflows operable
Architecture earns its place by helping real people use and change the system.
03
Design for change
Build enough structure to protect the product without premature complexity.
Chapter 04
05 / DEALS
05 / DEALS
State architecture
Predictable state makes mobile interfaces calmer.
BLoC/Cubit and Clean Architecture separate UI state, domain rules and infrastructure so product behavior remains predictable.
Presentation
Flutter adaptive UI
State
BLoC / Cubit
Domain
Product rules
Infrastructure
Firebase / local storage
Chapter 05
05 / DEALS
05 / DEALS
Firebase / notifications
Return loops are part of product architecture.
Authentication, messaging and product services connect backend events to the mobile experience.
DEALS
in use.
Interfaces, states and developer tooling are shown as evidence of product behavior rather than a technology logo collection.
05Structure
you can inspect.
The visual connects what a user touches to the decisions underneath it.
DEChapter 06
05 / DEALS
05 / DEALS
Offline
Mobile software has to survive imperfect connectivity.
Local persistence keeps important state useful when the network is unreliable.
Presentation
Flutter adaptive UI
State
BLoC / Cubit
Domain
Product rules
Infrastructure
Firebase / local storage
Chapter 07
05 / DEALS
05 / DEALS
Arabic / RTL
Localization is not post-processing.
Arabic support changes layout direction, alignment and interface assumptions.
DEALS
in use.
Interfaces, states and developer tooling are shown as evidence of product behavior rather than a technology logo collection.
05Structure
you can inspect.
The visual connects what a user touches to the decisions underneath it.
DEChapter 08
05 / DEALS
05 / DEALS
Cross-platform
Shared code does not mean identical UI.
Flutter allows shared product logic while interfaces remain adaptive to the target surface.
Discover
Shared code does not mean identical UI.
Save
Shared code does not mean identical UI.
Return
Shared code does not mean identical UI.
Use offline
Shared code does not mean identical UI.
Chapter 09
05 / DEALS
05 / DEALS
Ownership
Different surface. Same responsibility.
Deals proves the same ownership model works at a different scale: product, state, infrastructure and delivery remain connected even when the UI feels lighter.
Different surface. Same responsibility.
Different surface. Same responsibility.
Different surface. Same responsibility.