I’m spending more time building, what I’ve dubbed the CityGrid Local, Mobile, Social Stack, a list of APIs, platforms and tools that you can use in your local-mobile applications. Today I’m diving into Verizon’s LocationKit API which provides a unified library across platforms and devices that can be used to request location information.
Despite what you may think, the Verizon LocationKit API is not specific to Verizon devices, and supports a wide variety of Android, iOS, Blackberry and Brew MP devices. The LocationKit API supports two types of location requests:
- Single Request – Usually requested to get local search information or to place the device on a map
- Tracking Request – Used to show the position of the device on the map in real time or to navigate to a destination
- Standalone GPS (SGPS) uses the GPS chipset in devices that can obtain GPS information without network assistance
- Cell ID uses the location of the cell the device is currently talking to provide a quick approximate location that can be used to obtain local information
- Wi Fi ID uses the visible Wi-Fi networks that the device can see to obtain an approximate location that can be much more accurate than the Cell ID location
To obtain location information your application can request a single fix where the applications specifies how much time it is willing to give the hardware for obtaining the best possible location, or a multiple fix where your application requests a stream of fixes. When the desired request is submitted and a listener / callback is used to pass the information back to your host application.
The Verizon Mapkit API is a perfect addition to the CityGrid Local, Mobile, Social Stack. Location is essential in all local, mobile, social applications and the Verizon LocationKit is a robust, easy to use library you can use in your native app development, and in conjunction with the Verizon Mapkit API you can provide real-time location and rich mapping to your mobile application users.