Keep the catalog and cart on the device
AsyncStorage and NetInfo keep the app usable when the connection drops, so a customer doesn't lose their cart in an aisle.
The cost: Saved data can go stale, so the app has to know when it is offline.
Torbini & Dollar
A retail app with in-store QR scanning, shipped to both app stores.
- 6
- production screens
- 14
- reusable components
- 2
- app stores
The project
Torbini & Dollar is a retail app for use inside the stores. A customer scans a product's QR code, builds a cart, and gets a code to pay at the cashier. I was the primary developer, and I took it all the way through both app stores.
The problem
People use this app while standing in a store: they scan products, build a cart, and pay at the cashier with a code. The signal inside a store can drop, and a mistake in the cart means a wrong bill.
The decisions
Test the logic that touches money
Unit tests cover cart deduplication, QR encoding, API mapping and input validation, where a bug costs real money.
The cost: I didn't test everything. I picked the parts where a mistake hurts most.
Own the release as well as the code
I handled EAS builds, signing, the privacy policy and both store submissions myself.
The cost: Store reviews and release work take time away from building features.
Where it landed
Live on the App Store and Google Play, and already updated to v1.0.1.
What I did
- Built QR product scanning, catalog search, the cart and order generation across six production screens.
- Owned the release: Expo EAS Build and Submit, signing, store submissions and the v1.0.1 update.
- Added offline-aware catalog and cart persistence with AsyncStorage and NetInfo.
- Wrote Vitest unit tests for cart deduplication, QR encoding, API mapping and validation.