One codebase, both stores, and aweb app when the stores getin the way.
Flutter for iOS, Android and PWA, with the backend, payments, reliable push and offline sync your field staff need.
Roles from claims. Notifications once. Race conditions treated as bugs. Push is triggered on the server.
Everything the engagement delivers.
Each piece already runs for a client — nothing here is a slide.
Flutter application
Riverpod state, go_router navigation, a design system in widgets. One codebase, three targets.
Backend by fit
Firebase where its model fits; Next.js + Prisma where data is relational. In production · 8 Cloud Function triggers.
Payments
Stripe, open banking, in-app purchases, wallets with an audit trail. In production · Tide payouts.
Offline, media, location
Offline-first sync, camera pipelines, maps and places. Field-ready.
Push notifications
Server-side triggers, deduplication keys, delivery logs. Fires once.
Release
Store submission and review handling, or PWA with install prompts. Launch on schedule.
Roles from claims. Notifications once. Race conditions treated as bugs.
Push is triggered on the server
Deduplicated and logged, so a partner is told once — not twice, not never.
Roles come from custom claims
The app renders what the claim allows; the database rejects what it doesn't.
Writes are serialised and idempotent
Partner creation, wallet updates and payout status changes cannot double up.
PWA when review is a risk
Installable, offline-capable, instant updates, with a store route kept open.
Before you write to us.
Flutter or native?
+When is a PWA the better choice?
+Can it work offline?
+Firebase or custom backend?
+How are notifications kept reliable?
+Tell us what should
run itself.
Send the problem, not a brief. An engineer replies within one business day.
Start a project