The document discusses alternatives to using Google Maps for mobile apps. It lists technical requirements like supporting layers of complex content from multiple sources, large content size, and offline use. It also mentions business requirements like licensing, pricing and usage models, and custom branding. It then provides examples of existing mapping libraries like OpenStreetMaps, CloudMade and Polymaps. It also suggests writing your own custom map library to meet specialized needs. In summary, the document outlines reasons to consider alternative mapping solutions and provides examples of existing open-source and custom options.

1. Alternatives to
Google Maps
For Mobile Apps

2. That’s already there!
Why
alternatives
anyway?

3. Why Alternatives for Maps?
Technical Business
Requirements Requirements
Content
•Layers of information
Licensing
•Content size
•Illustration
Complexity
•Multiple sources
•Is it really a map?! Brand perspective
Behavior
•Offline support Pricing & Usage

4. What are alternatives?
 Try existing ones.
 OSM : OpenStreetMaps
 CloudMade
 Polymaps [Vector – SVG]
 Faster Imaging

5. What are alternatives?
 Write your own map library!
Themes
Roads Paths Lakes Etc.
Zoomlevel
Dataset X1 Dataset Y1 Dataset Z1 Dataset Q1
Dataset X2 Dataset Y2 <Null> Dataset Q2
Dataset X3 Dataset Y3 <Null> <Null>
Dataset Xn Dataset Yn <Null> Dataset Q3
DataProvider: B
DataProvider: A

6. Achieved!
Specialized Content
Multiple Content Providers
Super squeezed content size
Offline Support

7. Thank you!