A React Native library for checking if a location is inside a polygon using Google's Geometry library.
react-native-geo-fencing is a React Native library that enables geofencing by checking if a geographical point is within a defined polygon. It solves the problem of determining location boundaries in mobile apps, such as for delivery zones, restricted areas, or location-based triggers. The library uses Google's Geometry library under the hood for accurate calculations on both iOS and Android.
React Native developers building location-aware mobile applications that require geofencing, such as logistics, ride-sharing, or safety apps.
Developers choose this library because it provides a simple, cross-platform API to leverage Google's proven geometry algorithms, avoiding the complexity of implementing geofencing logic from scratch. It's specifically designed for React Native, ensuring seamless integration with existing projects.
Native modules to determine if a location is within defined geographical boundaries using Google Geometry library
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Leverages Google's Geometry library for high-precision point-in-polygon checks, as noted in the README's use of containsLocation from Google's APIs.
Implements native modules for both iOS and Android, ensuring reliable performance across platforms without relying on JavaScript-only solutions.
Offers a straightforward GeoFencing.containsLocation method that returns a promise, making integration easy with minimal code, as shown in the usage examples.
Works directly with navigator.geolocation to fetch device positions, enabling real-time checks without additional setup, demonstrated in the componentDidMount example.
Installation requires manual steps like editing Podfiles, modifying build settings, and linking libraries for both iOS and Android, which can be error-prone and time-consuming.
Only supports point-in-polygon checks; the README shows no capabilities for circles, dynamic zones, or background monitoring, limiting advanced use cases.
Relies on Google's Geometry libraries, which may introduce licensing issues or require API keys in some deployments, though not explicitly mentioned in the README.