react-native-fbsdk VS react-native-maps

GitHub Stars: 3k

I came to know that Facebook dropped the support from the official wrapper library and created Facebook SDKs for Android and iOS instead. But if you are only a JS dev you won't understand the swift code mentioned in their iOS SDK and you'll get confused like me.

Facebook announced that they ended support for Facebook SDK for React Native in this article. They claim that community is good enough to maintain this SDK. This version of README file of the repo says otherwise.

This means facebook stops officially supporting https://github.com/facebook/react-native-fbsdk. They are still working on react-native, do not worry !

We are using the code below. And we use https://github.com/react-native-maps/react-native-maps for Maps

Now for the fun part - understanding the relevant MapView props! When reading the full MapView documentation you can see the MANY props but we will only need the following:

Are you using react-native-maps own polygons? There is a “polygon creator” example on their github: https://github.com/react-native-maps/react-native-maps/blob/master/example/src/examples/PolygonCreator.tsx

And their docsdont seem to include any draw/edit functions.

Plus google isn’t going to charge you for the google maps mobile sdk. Discussed here https://github.com/react-native-maps/react-native-maps/discussions/4278

react-native-maps offers map components for your Android or iOS application. The kit offers different types of component API such as MapView, Marker, Callout, Polygon, Polyline, Circle, and Overlay.

GitHub Stars: 13.7k

react-native-maps is the best option for handling location and maps in react native. you can use openstreet, google maps, apple maps, or any other tile overlay. also, it provides some good examples in its repository which covers most of the use cases.