Work
Food delivery platform — four apps, one order flow
A food-delivery suite for a Swedish operator: customer, courier and restaurant apps in Flutter plus a web admin — the full loop from order to doorstep, owned rather than rented from a marketplace.
Flutter · Dart · Laravel
- Context
- A Swedish food-delivery operator running its own platform instead of paying marketplace commissions — which means owning every surface an order touches.
- Problem
- One order involves four roles — customer, restaurant, courier and operations — each needing its own application, kept in sync as the order moves.
- Constraints
- A small team carrying four codebases; mobile releases gated by app-store review, including mandated privacy and account-deletion pages; confidentiality on the operator.
- Role
- Lead developer across the suite — top committer overall, verifiable per repository.
- Architecture
- Three Flutter applications (customer, courier, restaurant) sharing conventions, and a Laravel-based web admin for operations. Public compliance pages (privacy policy, account deletion, terms) are maintained alongside the apps.
- Key decisions
- Flutter across all three mobile apps so one small team can hold the whole surface area with one language and one toolchain. A deliberately boring server-rendered admin — operations tooling needs reliability, not novelty.
- Outcome
- A complete four-surface suite with store-compliance pages published. Order volumes are the operator’s and are not published here.
- Evidence
- Private repositories; contribution history verifiable per app. References available on request.
- Confidentiality
- The operator is not named here.