Originally Posted by Bsginc
Google has guaranteed that apps will not use the Google APIs. Developers cannot afford the overhead if app becomes too popular.
Of course, in the land of unintended consequences, it could help to drive Yelp! out of business, thus depriving Google with important restaurant reviews for use by it's own services.
Out of curiosity, I wonder how many developers built a click counter into their apps to monitor the number of hits on a Google map. Or do they just depend on Google to count for them.
And, I wonder how this will impact realty companies and MLS services as well.
Should also point out that, if you want to use a portion of a Google map on your website, or otherwise copy it for use elsewhere, you have to obtain an annual license from Google. Last I looked, that was a $400 hit to the wallet. Will the hit charge be on top of that?
This is an interesting post from several perspectives.
Let me toss in another tidbit of information that may help clarify or muddy the discussion.
A map is a map is a map.... ...mostly just static information that you can focus on (pan zoom, etc).
Where a map starts to become interesting is when you or your interests become highlighted on that map.
We used to trace our route/progress with colored markers on a paper map -- that we kept folding and unfolding to see where we were, where we were going and what around us was interesting.
Now, we have phones and tablets with GPS and wireless connections that can do all that for us -- and more: directions; distances; alternate routes; turn-by-turn instructions... they even give us updated traffic and road/weather conditions...
So, what's left to do to maps to make them more usefull?
There may be quite a few things... but here are two:
When Apple bought PlaceBase I visited the site and spent some time going through the examples.
You can do a limited amount of this with current maps -- but PlaceBase offers almost complete customization, e.g. a map of the US just showing mountains, lakes and state capitals -- no roads, points of interest... no nuthin'.
The other thing that PlaceBase has going for it is that it has [contractual ?] arrangements to get access to and map/present demographic data.
So, now you the user (or an app on your behalf) can create custom maps showing demographic overlays. Things such as:
-- average household income
-- number of people per household
-- number of employed per household
-- number of square feet, bedrooms, bathrooms, etc. per household
-- number of automobiles per household
-- military service
-- televisions per household
-- computers, smartphones, iPads per household
-- political affiliation
-- education level
-- population density
-- Number of Android Activations per device
... Well maybe not the latter
Anyway, there are lots of different uses for this dynamic programmability and demographics tied to maps.