react-native-google-maps-services
Feb 2018 to ongoing...
React Native Client for Google Maps Services
repo

This is a fork of google-maps-services-js that removes as many core Node.js modules as possible to allow developers to use the library in React Native without the need for shims via projects such as node-libs-react-native, ReactNativify, or rn-nodeify.

The current implementation leverages axios to replace http/https and adds the following dependencies:

A detailed explanation of what was changed and why can be read here in my blog post here: Forking google-maps-services-js. It also goes into depth on what functionality was removed. For example, there is no cli anymore since that is not needed by React Native.

Disclaimer

While this current works, there are several outstanding issues that I need to fix before this can be considered production ready. A short list of the biggest issues are:

Intro

This library brings the Google Maps API Web Services to your React Native application.

The React Native Client for Google Maps Services is an axios backed Client library for the following Google Maps APIs:

Keep in mind that the same terms and conditions apply to usage of the APIs when they’re accessed through this library.

Features

Quick Start

$ npm install react-native-google-maps-services

Note: You’ll need to have npm 2.7.0 or greater installed, since this library is hosted as a scoped package.

Create a new client object by calling createClient()

123
var googleMapsClient = require('react-native-google-maps-services').createClient({
  key: 'your API key here'
});

Make requests to the Google Maps APIs by calling methods on the client object.

12345678
// Geocode an address.
googleMapsClient.geocode({
  address: '1600 Amphitheatre Parkway, Mountain View, CA'
}, function(err, response) {
  if (!err) {
    console.log(response.json.results);
  }
});

For more usage examples, check out the tests.

View the reference documentation

Additional documentation for the included web services is available at https://developers.google.com/maps/.

API keys

Each Google Maps Web Service request requires an API key or client ID. API keys are freely available with a Google Account at https://developers.google.com/console. The type of API key you need is a Server key.

To get an API key:

  1. Visit https://developers.google.com/console and log in with a Google Account.
  2. Select one of your existing projects, or create a new project.
  3. Enable the API(s) you want to use. The Node.js Client for Google Maps Services accesses the following APIs:
    • Directions API
    • Distance Matrix API
    • Elevation API
    • Geocoding API
    • Places API
    • Roads API
    • Time Zone API
  4. Create a new Server key.
  5. If you’d like to restrict requests to a specific IP address, do so now.

For guided help, follow the instructions for the Directions API. You only need one API key, but remember to enable all the APIs you need. For even more information, see the guide to API keys.

When you have an API key, you can create a client object:

123
var googleMapsClient = require('react-native-google-maps-services').createClient({
  key: 'your API key here'
});

Client IDs

Google Maps APIs Premium Plan customers can use their client ID and secret to authenticate, instead of an API key.

1234
var googleMapsClient = require('react-native-google-maps-services').createClient({
  clientId: 'Add your client ID here',
  clientSecret: 'Add your client secret here',
});

Important: This key should be kept secret on your server.

Developing

In order to run the end-to-end tests, you’ll need to supply your API key via an environment variable.

$ export GOOGLE_MAPS_API_KEY=AIza-your-api-key
$ npm test

Support

This library is community supported. We’re comfortable enough with the stability and features of the library that we want you to build real production applications on it. We will try to support, through Stack Overflow, the public surface of the library and maintain backwards compatibility in the future; however, while the library is in version 0.x, we reserve the right to make backwards-incompatible changes. If we do remove some functionality (typically because better functionality exists or if the feature proved infeasible), our intention is to deprecate and give developers a year to update their code.

If you find a bug, or have a feature suggestion, please log an issue. If you’d like to contribute, please read How to Contribute.