Case study
WhatsApp orders without Meta Cloud API fees
Usual path
Teams burn months on Meta Cloud API verification and then pay ongoing message costs for basic customer notifications and order flows. For a Pakistani restaurant that already lives on WhatsApp, that tax is real.
What I built instead
A native Android APK with a background Notification Listener Service, plus NDK where performance mattered. The phone intercepts incoming order texts, decodes them, and pushes structured orders into the central SQLite WAL database — same ERP the POS already uses.
Result
Orders run on ordinary Android hardware. No Meta verification gate for this path. Message cost for that pipeline: $0. Independence from Meta's monetization funnel for day-to-day order taking.
Why NDK + listener, not a script
This isn't a fragile chatbot glued to a webhook. It's an order-taking stack: notification engine, voice STT where needed, Order Mode vs Friend Mode, parallel chat handling. NDK sits under the hot path so the device stays responsive when nights get busy.
Honest limits
This design trades Meta's managed API for device ownership and OS permissions. You need a dedicated shop phone, careful battery/permission handling, and ops discipline. I don't claim "unlimited free WhatsApp forever for every use case" — I claim a production order path that shops can run without Meta Cloud billing for those messages.