A local food app where the commission flows back to people
Delivery platforms take a commission on every order and keep the relationship with the customer. Istigos started in Timișoara with a different deal: part of what restaurants pay goes back to the people who order and to the friends who brought them. The slogan on the flyers was "the new Timișoara app where you get real cashback".
Save on every order
A discount wallet that lowers the bill at partner restaurants, plus cashback you can spend in the app or withdraw to your bank account. No vouchers.
Earn for life
Invite friends and you get 10% of the Istigos commission on every order they place, for as long as they order. Their friends bring you another 2%. The more people you invite, the more you earn.
Grow their own regulars
Each partner handed out flyers with its own referral code: new customers got a 5–10% discount there, and the restaurant became part of their network. Restaurants pay a commission per order, with a different rate per channel.
Dine-in was part of the same system. A guest at the table shows a personal QR code, the waiter scans it, and the meal earns discount and cashback like an online order, so walk-in guests could join the network too.
One product, four moving parts
Customers and restaurants each had their own app. A headless CMS was both the API and the back-office. A small Node.js service handled identity and the emails every order sends.
From a craving to a confirmed delivery time
Real screens from the running system, in order. Ana orders two pizzas. The restaurant confirms with a delivery time. Ana is emailed and accepts the time in the app.
Scroll sideways →
- Customer

Wallet first
The home screen opens with the two balances: discount (339.88 lei) and cashback (245.56 lei).
- Customer

Menu by category
Each product has delivery, pick-up and dine-in prices, portions, extras and allergens.
- Customer

Cart
The cart is a snapshot. A later menu change never rewrites the order.
- Customer

Spend the wallet
Two sliders: discount first, capped by the restaurant (7% here), then cashback. 83 lei becomes 30.88 lei.
- Customer

Cash or card
Card payments go through the bank's 3-D Secure page.
- Customer

Sent Nou
The order waits for the restaurant.
- Restaurant

Live queue
The tablet app polls the queue and plays an alert sound for new orders.
- Restaurant

Order detail
Items, notes, discount and cashback used, amount to collect, address.
- Restaurant

Confirm with ETA NeConfirmata
Confirming means promising a time. 30 minutes is picked here.
- Email service

Customer is emailed
The auth-mail-api sends the branded confirmation email with the order summary.
- Customer

Accept the time Confirmata
Ana sees "ready in 30 min" and accepts. Only then does the kitchen start.
Headless CMS as both API and back-office
Strapi gave the operations team an admin UI and gave the apps REST and GraphQL from the same schema. Identity and email lived in a separate Express service, so the CMS could be upgraded on its own.
Configuration as code
Roles and the permission matrix are applied at boot by bootstrap.js, so a new database behaves like production. All URLs, keys and secrets come from environment variables.
Business rules as data
Bonus amounts, premium tiers, commission rates and discount caps live in the CMS. The business can change them without releasing a new app version.
OTA delivery
Store builds came from EAS. JavaScript fixes reached every phone in minutes through expo-updates, without store review.
A state machine shared by three actors
The customer must accept the restaurant's proposed time before cooking starts. Nobody waits for an order without knowing when it will arrive, and a refusal costs the kitchen nothing.
Where the money goes on a 100-lei order
Restaurants pay a commission that depends on the channel. Part of it becomes cashback for the customer's referral chain, up to six levels deep. Every movement is written to a ledger, so any balance can be explained to a customer.
Discount caps reward discovery
Each restaurant sets four caps: General, and lower ones if the customer ordered there in the
last 1, 3 or 7 days. New customers get the best deal. Regulars still get a deal, and the restaurant keeps its margin.
Three delivery zones
Each zone has its own minimum order, fixed fee and per-km fee. The app computes the zone from the saved address and hides restaurants that are too far away.

Operations ran from the CMS
Onboarding a restaurant (menus, photos, hours, fees) happened in the admin UI, without code changes. The GraphQL schema is generated from the same content types.




Built for a busy counter
Big colour-coded tiles per state, a sound for every new order, a countdown to the promised time, and reports that match the monthly commission statement.

Staff login
A role decides the home screen: manager, waiter or driver.

New orders
Channel, payment method, amount and the "seen by" marker.

Day history
Every order of the day, grouped by state.

Reports
Per driver, per period, per channel.

Period report
Cash, card, discount, cashback and the platform commission.
As customers saw it
The original App Store and Google Play artwork, made by a designer colleague.
What I would build differently today
The product was built fast, by one developer, to prove a business model. Many of these trade-offs were deliberate. This is the plan I would follow now.
| Then | Risk | Today |
|---|---|---|
| Cashback and commissions computed in the apps | Not atomic. Clients are trusted with money movements | A backend service owns state transitions and writes order, ledger and commission in one transaction |
| Public role can write customer records | Anyone who knows the API can change another customer's data | One identity provider. The API verifies the JWT and enforces ownership per row |
| GraphQL built by string interpolation | Injection, fragile queries | Variables and typed operations generated with graphql-codegen |
| Two services share one collection | Silent schema drift | One owner per collection. The other service reads an API or receives events |
| Card payments started in the app | Merchant credentials in the client bundle | The server creates the payment session. A webhook confirms payment |
| Polling every 10–20 s | Latency and wasted load | WebSocket or SSE push, with polling as fallback |
| Strapi 3, Node 14, Expo 47 | End of life | Strapi 5 or NestJS + PostgreSQL. Latest Expo with Expo Router. TypeScript, tests and CI |
The whole system runs locally
The repository has a Docker Compose stack (MongoDB, Strapi, the auth and mail service, and a Mailpit inbox) and a seed script. The seed creates three fictional restaurants, staff accounts, customers with a referral tree, and 40+ orders in every state, all through the public APIs.
| Component | Stack | Path in the repo |
|---|---|---|
| Customer app | Expo SDK 47, React Native 0.70, MobX State Tree | apps/customer-app |
| Restaurant app | Expo SDK 47, Redux, react-native-paper | apps/restaurant-app |
| CMS / API | Strapi 3.6, GraphQL, MongoDB | services/cms-api |
| Auth & email | Express, JWT, Nodemailer | services/auth-mail-api |
| Demo stack | Docker Compose, seed scripts, Mailpit | infra/ |