finds.dev← search

// the find

react-native-maps/react-native-maps

★ 15,961 · TypeScript · MIT · updated Apr 2026

React Native Mapview component for iOS + Android

The de-facto standard map component for React Native, wrapping both Apple MapKit and Google Maps behind a unified declarative API. If you're building a React Native app that needs a map, this is almost certainly the package you'll end up using — there's no serious alternative with comparable feature coverage.

Full New Architecture (Fabric) support landed in 1.26.x, which puts it ahead of many community libraries still stuck on the old bridge. The child-component API (Marker, Polyline, Polygon, etc. as JSX children of MapView) is genuinely intuitive and maps well to how React developers think. Tile overlay support — both URL-template and local xyz tiles — is solid enough to build offline map features without reaching for a separate library. The example app covers ~40 distinct scenarios, which means most integration questions can be answered by reading source rather than StackOverflow.

Maintained by a small group of volunteers, and the issue backlog reflects it — expect open bugs to sit for months. The Android marker animation path is a known gap: the Animated API works on iOS but falls back to a native imperative call on Android, and the README just shrugs at it. Custom view markers on Android are rendered as bitmaps, which means any React re-render triggers a full re-rasterize — put more than ~50 of them on screen and you'll feel it. Google Maps on iOS requires a separate CocoaPods dependency and a cloud-configured Map ID for styling, making initial setup meaningfully more complex than the Apple Maps path.

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 →