Please explain how releasing a maps application on a platform where the user is 100% free to download another maps application from the app store is considering "shoving it down the users throat." Oh wait, its not. You're just over reacting.
Preventing me from setting a different "default" application is shoving a specific app down my throat - i'm "forced" into this app when using secondary functions and prevented from using the normal personal assistant system for my "other" maps app... like forcing me to use Safari, like forcing me to use Apple Mail... get the picture?
Shoving it down your throat would be eliminating all maps apps on the app store and making Apple maps the only available application. But we both know that is not the case.
No - that would be shoving it down my throat and forcing me to digest it.
I think the average user will update to iOS 6 and not totally know the difference. The average user will open up maps and think "Oh it looks different. And I can do turn-by-turn now!"
You should get out more - meet some "average" users, they have noticed.
The average user doesn't spend hours reading macrumors and tech blogs like people on here do. Thus they will most likely not know what the major differences are. They will see added turn-by-turn and added 3D. Let's face it, the average user is not tech savvy.
The "average" user might just try and use the maps app - in most of the world it would be impossible for them to go somewhere or simply find things. They don't go on MacRumors but they do go on Facebook, Tumblr, you name it... and they do cry out in vain.
So if Apple just made it an opt-in scenario and made Google Maps default and Apple maps an option in settings, then most people wouldn't use Apple maps. And without users, there would be nobody to find bugs and issues. So this optional preview you mentioned would not be nearly as effective.
Not my problem, seriously something Apple should have thought about before they unleashed this turd upon their users. When the Google Maps app land - people will go back to using that, only fanboys like you and Apples Cupertino staff will update Apple Maps with new POI's...
The most expensive and time consumer part of developing is not the initial release, it is keeping the software up to date after initial release. That is the most important part. And with people using the software, the developers know what to fix.
And exactly where Apple really screwed up - not only by having a half baked product but also in having piss-poor interfaces and options for editing vital information - "average users" will never submit anything into that clunky interface, because it's downright bad. There's no OSX version, theres no web interface (bigger screen, mouse and keyboard are so much better when doing overlays or a large amount of POI's) and we don't even know if Apple are doing some sort of quality control on this at all. A company that knows what they are doing would have this under control - Apple doesn't.
No matter what, in an ideal situation developers will fix all problems in a program/app. The more people you have using the program, the sooner you will find all problems that need to be fixed. The less people you have using the program, the longer it will take to fix everything.
We're not talking a bug in an app here - one fix will only apply to a few users. And stock software doesn't come out with 10 million+ missing "features" or "bugs", so it's not comparable.
What is keeping you from providing feedback now? Apple has made it very easy to provide feedback for their maps. Even Google offers easy ways to provide feedback. The reason both offer ways to provide feedback is because it is never going to be perfect. I would love to see you team up with people to make a detailed map of the entire world. Then when you think you are done, release it and see if you are ever actually finished.
The way of providing feedback is in no way effective and is actually keeping me (discouraging me) from providing proper feedback. It's not comparable to the way you submit feedback to Google, because they have this in working condition - try reading up on what those differences are before comparing two widely different approaches.
And why the hell should "he" make his own maps app? Unlike Apple "he" didn't go around telling the would that "he" could make the perfect maps app while on the toilet...
Last edited: