Choosing Your Distance Integration
Select the best way to integrate Woosmap Distance in your product.
This guide helps you choose the right integration path for your project. Find your use case in the summary table below or jump to a specific section for details.
Choose Your Integration Path
| If you’re building… | Use This | For… |
|---|---|---|
| A backend | REST API | Full, platform-agnostic control. |
| A location-aware web app | Map JS API | The recommended, unified map and search solution. |
| A mobile app | Native SDK | iOS or Android applications |
1. REST API
For any non-browser environment, the REST API is your starting point. It provides direct, platform-agnostic access to the core Distance engine.
- Use it for: Backend services, mobile apps, or data processing.
- Key benefit: Full control with a secure, private API key.
2. Map JS API (Recommended for Web)
This is the primary, forward-looking solution for building location-aware web applications. The Map JS API includes a
powerful DistanceService that unifies both mapping and routing into a single, seamless library.
- Use it for: Applications requiring interactive map functionalities, including searching for locations and generating detailed route itineraries.
- Key benefit: A single, powerful library for all your location needs on the web.
3. Mobile Native SDK (Recommended for Mobile Apps)
This is the best way to integrate Woosmap’s technology into your mobile apps.
- Use it for: Applications for iOS or Android, you can use our Native SDK or the React and Flutter ones.
- Key benefit: Easy to use when you need to integrate several Woosmap services.