Problem
Companies that run their own delivery fleets still plan routes and track drivers in spreadsheets and group chats. Their drivers get none of the experience people expect from modern delivery apps.
Role
CTO (founding engineer)
What Avi built
Share product direction with my co-founder and own engineering across web and mobile. Built the iOS/Android driver app from scratch with Expo, sharing delivery logic with the web app over one typed API. Built order imports from Google Sheets, CSV, and Excel, multi-language support including right-to-left, and the AI software factory we use to build the product.
Outcome
Live at yarcone.com. Features are shaped by rounds of user feedback and test runs with real delivery data, and shipped by agents that take tickets through implementation, review, testing, and merge.
The driver app has to keep working on phones that haven’t updated yet, so the API only changes additively and the server sets a minimum app version.
Highlights
- Native driver app with route, proof-of-delivery, and cash handling logic shared with the web app.
- Order imports from Google Sheets, CSV, and Excel through one resumable, undoable pipeline.
- Customers messaged over WhatsApp with SMS fallback, in their own language, including Hebrew and Arabic.
- An agent pipeline across several machines: tickets go through implementation, review, testing, and merge, and decisions that need a human come back to us.