NibblifyThree perspectives. One product.
Supplied product mockups. Figures shown in the interfaces are demonstration content, not reported business results.
Engineering focus
Each participant needs a different interface, while orders and operational data must stay connected.
The implementation
Flutter and Dart power the apps. Firebase provides shared data and backend services. The staff portal supports internal operations; the website introduces the product.
Current release
Food, Partner and Driver are published on the App Store and Google Play. The official website says customer ordering has not started yet; delivery in Le Mans is being prepared.
Decisions behind the interface
Consistent checkout totals
The customer backend uses shared pricing logic for checkout preview and order creation. A total-drift guard rejects a changed price instead of accepting an amount the customer did not confirm. The repository includes pricing-parity integration tests.
Search across scripts
The search implementation normalizes Latin accents and Arabic letter variants on both queries and indexed content. Typo-tolerant matching helps restaurant and dish discovery without treating every spelling variation as a new term.
Operations are a separate surface
The Flutter Web staff portal contains restaurant verification, order support and driver-management interfaces. It is an internal operations tool, distinct from the three public store apps. The public website uses a static HTML/CSS build rather than Flutter.
Discover restaurants, explore menus, and order food.
Manage orders, menus, and restaurant performance.
Manage deliveries and keep track of earnings.
- Nibblify FoodApp Store ↗Google Play ↗
- Nibblify PartnerApp Store ↗Google Play ↗
- Nibblify DriverApp Store ↗Google Play ↗