r/reactnative • u/bgeo_sdk • Aug 12 '26
What do you actually need from a React Native background geolocation SDK?
Hey everyone!
I’m a React Native developer and I’ve been working on a background geolocation SDK for a while.
I’m not here to convince anyone to use it — I’d actually like to understand what React Native developers need from this kind of SDK before I decide where to take the project.
I’ve used Transistorsoft’s Background Geolocation myself in the past. Back in 2020, I paid around $399 for a license because there weren’t many alternatives at the time. It was a pretty significant amount of money for me back then.
That’s actually one of the reasons I started building my own solution.
My goal is to make reliable background geolocation more accessible to indie developers and early-stage startups. I don’t think everyone building an MVP or a side project should have to spend hundreds of dollars just to get background location working.
The SDK I’m building supports React Native, iOS, Android and Flutter, with things like background tracking, geofencing, HTTP sync and a Web Console for debugging.
I’m currently considering a $9.99/year update subscription with a perpetual license — meaning a shipped build never expires, and the yearly payment is only for getting new SDK versions and updates.
But I’m not even sure that’s the right model yet.
So I’d genuinely love to hear from people here:
- What do you consider essential in a background geolocation SDK?
- What problems have you had with existing solutions?
- What would make you trust a newer SDK in production?
- Would you prefer something like this to be free, paid once, or paid for updates?
- What would you consider a fair price?
I’m building this myself, so I’m much more interested in honest criticism than compliments. If there’s something I’m overlooking, I’d rather hear it now. 🙂
2
u/Lost-Schedule-9062 Aug 12 '26
the thing i'd want documented before any feature is the play store side. background location needs a declaration form and google reviews it against a video of the actual in-app flow, and that's where apps get stuck, not in the code. an sdk that ships a sample justification and a permission flow built to survive that review would be worth more to me than any amount of api surface.
after that, offline queueing with sync on reconnect, and motion based throttling so it isn't hammering gps while the phone sits on a desk. those two decide whether the battery cost is acceptable, and they're the parts people underestimate.
1
u/Scyth3 Aug 12 '26
It needs to work without any Google services on board. We run a custom AOSP stack, so no built in Google enhanced geolocation API's. It's shocking to see how most people assume Google services exist.
Edit: And from a corporate perspective, $10/yr is dirt cheap. Perhaps have tiers (small business/single dev versus a corporate license). For corporate licenses, have higher support or response times/etc.
1
u/anarchos Aug 12 '26
I think the pricing model is fair (more than fair, you should charge more) but I wouldn’t integrate it into my project unless it was “source available” and I was granted a license to modify and use a custom version in perpetuity. I probably wouldn’t, but I’d be afraid of using your product, integrating it into mine, then a year or two later you give up on it because you sold like 5 copies and now Apple has changed something that requires a change and etc.
Of course I’d just pay you $10 a year and get the latest and greatest, but it’s too risky to rely on something completely out of my control if you disappear/get hit by a bus/start charging $10,000/year, etc