Contact person: Expo Geofencing Background Tracking

Phone:Show

Email:Show

Location: Sydney, Australia

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"My React Native Expo app, Spotted, needs a reliable background-location layer that stays alive on both iOS and Android and fires geofence events even when the app is suspended or killed. I already have the core screens and API calls in place; what’s missing is the service that registers geofences, requests the right permissions, and wakes the app up as soon as a user crosses a boundary.

The workflow I picture: when a user opens Spotted, we download a set of longitude/latitude radii from our server, register them with the OS, and silently post an event back to the backend whenever an enter/exit occurs—no foreground UI required. Expo’s TaskManager / expo-location (or any equivalent native module you recommend) is fine as long as we stay inside the managed workflow or use a painless config-plugin that still lets us publish through EAS.

Acceptance criteria
• Runs continuously in the background on iOS (including after force-quit) and Android (Doze-mode friendly).
• Triggers enter/exit callbacks within 2–3 seconds of crossing a 100 m radius.
• Handles permission prompts gracefully and degrades to foreground-only tracking if the user refuses “Always”.
• Exposes a clean TypeScript API: registerGeofences(array), removeGeofences(), onGeofenceEvent(callback).
• Passes a simple demo: three hard-coded regions around a user’s location, with console logging confirmed in TestFlight and Play internal testing tracks.

If you have shipped background geofencing in an Expo or plain React Native app before, let me know how you solved the common headaches (permission fallbacks, battery drain, manufacturer-specific quirks) and roughly how long integration took on your last project." (client-provided description)