Tokkatok V2
Marketplace mobile rebuild shipped
$30-55
USD/hr direct (60% below US on-demand)
iOS + Android
Cross-platform first, native when needed
Why hire on-demand-experienced mobile devs from the Philippines
Real-time geolocation is harder than it looks
Battery-efficient location tracking, foreground vs background permissions on iOS + Android, geofencing, route optimization, ETA calculation. On-demand-experienced devs have shipped this and know the gotchas.
Dual-sided app architecture (consumer + provider)
Two apps with shared backend, different UX flows, real-time state sync (driver accepts → consumer sees update). Vetted bench has shipped dual-sided apps as a unified codebase or separate apps with shared services.
Dispatch + matching logic on the mobile side
Provider-side notification handling, accept/reject flows, route batching, surge pricing display, multi-stop logic. The mobile UI for dispatch is unforgiving — vetted devs have shipped it.
$30-55/hr — 60% below US on-demand mobile rates
US on-demand-experienced mobile devs run $100-160/hr. Same profile in Manila: $30-55/hr direct.
What this engagement covers
- Senior cross-platform mobile engineers with shipped on-demand / marketplace apps
- React Native or Flutter for cross-platform; Swift / Kotlin for native depth where needed
- Real-time geolocation with battery-efficient strategies
- Dispatch and matching algorithm integration on the mobile side
- Dual-sided app design (consumer + provider apps from one codebase or paired)
- Payment integration with splits (Stripe Connect, Xendit, PayMaya marketplace patterns)
- Ratings, reviews, and dispute workflows
- Push notification + in-app messaging architecture for real-time coordination
Frequently asked questions
How do they handle real-time geolocation efficiently (battery + permissions)?
On iOS: significant location changes for background, full GPS only when app is foreground. On Android: foreground service with persistent notification when tracking is active. Both: geofencing for arrival detection rather than constant high-accuracy polling. Vetted bench knows these patterns.
Dual-sided apps — single codebase or separate apps?
Depends on UX divergence. If consumer + provider UX is mostly different (Uber pattern), separate apps with shared backend wins. If UX is similar with mode switching (Airbnb host/guest pattern), single app with role-aware screens wins. Vetted bench has shipped both and can articulate the tradeoff.
Payment splits — Stripe Connect, Xendit, or custom?
Stripe Connect is the modern default for US/CA/AU marketplaces — well-documented split-payment, KYC handling, dispute flow. Xendit is the PH equivalent with similar features. Custom split logic only when neither fits (rare). Vetted bench has shipped at least one of these in production.
Have they shipped marketplace dispute and support workflows?
Yes — refund triggers, partial refunds, provider penalty workflows, support chat embed (Intercom, Zendesk SDK, Helpshift). The unsexy but critical part of marketplace ops. Vetted bench has shipped this.
How fast from "we need an on-demand mobile dev" to onboarded?
Typical: shortlist in 7-12 business days (on-demand experience filters the bench), interviews over 1-2 weeks, paid trial week immediately. End-to-end usually 4-5 weeks.
Ready to talk specifics?
30 minutes, no slides, no pitch — just a working session on your engagement.
Book a Discovery Call →
John from California
just requested a quote
2 minutes ago