ABSTRACT

The success of an application can make or break the amount of users who download, use, and recommend an app. Similarly, the performance, reliability, and availability of mobile network architecture and its trac ow are just as important, if not more important, to the success of an app. Chapter  2 described use cases for location services and also introduced the level of functionality behind the framework for location services. Obtaining user location from a mobile device is oentimes complicated. Not only are there multiple platforms to consider when developing, but there are also multiple options to choose from when building on top of a platform application programming interface (API). In this chapter we will cover one way to build these capabilities into your app using the classes of the android.location package.* e model described in this chapter, pictured in Figure 12.1, provides multiple entry points for a single app and invokes the individual use of components. Chapter 3 listed the various operating systems (OSs), discrete platforms to build apps on particular devices, and touched on the fundamental concepts to consider when choosing a platform, framework, or device. For the developers using framework API, or for those who are just starting to add

CONTENTS 12.1 GPRS Support Node and Network Switching Subsystem 218 12.2 Android Location Services 219

12.2.1 Request User Permissions 221 12.2.2 Challenges in Determining User Location 221

12.3 Summary 222

location awareness to their apps, you should strongly consider using the Google® Location Services™ API, and this chapter will cover Google Maps and Google Location Services API.