finds.dev← search

// the find

bramus/react-native-maps-directions

★ 1,280 · JavaScript · MIT · updated Jun 2024

Directions Component for `react-native-maps`

A thin React Native component that wraps the Google Maps Directions API and renders the route as a Polyline on a react-native-maps MapView. Handles waypoints, travel modes, and route splitting. If you need turn-by-turn routing on a map in a React Native app and you're already paying for Google Maps, this saves you the glue code.

Accepts origin/destination as coordinates, address strings, or Place IDs — the flexibility is genuinely useful. The splitWaypoints option automatically batches requests when you exceed the 10/25 waypoint API limit, which is the kind of edge case you'd otherwise hit in production and have to fix yourself. Polyline props pass through directly to react-native-maps, so you're not fighting a wrapper to change stroke color or width. The onReady callback returning distance, duration, and the full coordinate array gives you enough to build camera-fit behavior without additional API calls.

Last commit is June 2024 and the repo is essentially in maintenance mode — no active development means you inherit any react-native-maps breaking changes yourself. Hard-coded to Google Maps Directions API only; MapKit (listed in topics) is misleading, there's no Apple Maps routing path. No caching of fetched routes, so toggling a waypoint re-fetches everything from the API, which adds latency and burns quota. TypeScript types are a single hand-maintained index.d.ts file that lags behind the actual props — splitWaypoints shows as not present in older type versions.

View on GitHub →

// want more like this?

We dig through GitHub every week and send a few repos picked for what you actually care about — each with an honest take like this one.

Get finds in your inbox → Search again →