Hey Dawn, > The crucial question is really whether the app is freely available to > all, not just whether the map API key is hosted on the web. I don't > know if your app is anything like this, but in the iPhone app I was > contemplating, I would have put up a naked map on the web with no > controls, and then manipulated it on the phone, set the center to the > user's current gps location, let the user drag the map, and then > retreived the new center. In this case, the useful part of the app > lives on the phone, not at the url where the map is retrieved from.
Exactly - so this was why I was thinking you can't use Google Maps. Its a real shame, because it would be a great mapset to use. I'm not sure whether this http://code.google.com/p/iphone-google-maps-component/ allows you to get around the TOS because the functionality is still web-based - its just the "touching" of the iphone screen that controls the map. It's really confusing and I wish Google would just set the record straight. I don't want to go to the effort of coding in Google maps - only to have someone from Google write me a note saying "You are breaching our TOS". Rather not even use their maps from the start and stick with Windows Live maps - which don't have such "ambiguous - you can use it when we see fit" restrictions. It's too much effort for a developer to code everything only to have it ruined by TOS. I think the "uncertainty" and "lack of direction and clarity" from Google will make me move to Yahoo/Microsoft maps. Cheers --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to Google-Maps-API@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
