ShopConnect · retail software
An offline retail app with four roles in one Android build
· 4 min read
ShopConnect is an offline-first Android retail app that puts four roles in one build: customer, shop, rider and admin. Ankush Yadav built it in React Native and TypeScript with no backend, so one order can move through every role on a single device without a network call.
Why put four roles in one app?
A small retail operation has four kinds of people: the customer who orders, the shop that packs, the rider who delivers and the person who keeps it all within the rules. Most systems give each of them a different app and a server in the middle.
ShopConnect keeps them in one Android build. A role switch changes the screens, not the data, so the same order is visible from every side. That makes the flow easy to show, test and hand over, because nothing depends on a server being up.
How does an order move through the roles?
The customer picks a shop, adds items and places the order. The shop sees it arrive, accepts it, packs each item and hands it to a rider. The rider picks it up and marks it delivered. The admin sees every state change as it happens.
- Customer: browse a shop, build a basket, place the order, follow its status.
- Shop: accept the order, pack each item, hand it over; stock goes down when it is packed.
- Rider: see the assignment, pick up, deliver.
- Admin: totals across shops, customers, riders and orders, plus the compliance gates.
What does offline-first mean here?
The app makes no network calls. Shops, products, orders and their states live on the device, so the app works the same in a basement shop with no signal as it does on office Wi-Fi.
It also means nothing leaves the phone by accident. There is no payment provider to misconfigure and no customer data on a server to leak.
How are risky features kept switched off?
Retail touches money and restricted goods, so the app has a compliance gate. Real checkout and real payment stay switched off, restricted items such as cigarettes are locked and cannot be ordered, and the admin screen shows each flag so nobody has to guess what is enabled.
The ordering rules are covered by tests that run with Node's built-in test runner, so a change that breaks the flow fails before it reaches a build.