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?
Except for the fact that you can easily get sparrow or chrome. Apple not letting you choose a default program on iOS is no surprise, when have they ever allowed it? Why are you surprised now? Have you never realized that Apple has never allowed this before? Or did you think iOS 6 was all special and magical?
If you are trying to make a point, it is going completely against Apples history, and you need to do a little more research.
No - that would be shoving it down my throat and forcing me to digest it.
I don't know if you know this, but if something is being shoved down your throat, you are at the same time being forced to digest it. They are one in the same. If I am am shoving food down your throat and my entire hand is in your throat, you are also being forced to digest it. There is no other option. You have to digest it. You can't throw it back up because I am forcing it down with my hand. They are no different. So again, what I said is them forcing it down your throat. There is no difference between the two.
You really seem to not think things through.
You should get out more - meet some "average" users, they have noticed.
The average user hasn't. The average MacRumors and other tech blog readers have. There is a difference.
Again, you didn't think this all the way through.
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.
No, the average person who reads about it on Facebook will just skim over it and continue with their life. They don't cry out in vain. The people who cry out in vain are people like you, doing what you are doing right now. Reading MacRumors and other tech blogs.
The only people I have seen on my Facebook that post about this thing are people who are constantly on tech blogs. The people who post, also constantly on tech blogs. Not once have I seen what I consider an "average" user post anything like this. They just post pictures of their pets and dinner.
I am seeing a pattern with you. It makes me laugh.
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...
I am guessing you don't remember Google maps when it first came out haha.
Every map solution sucks at first. Pretty much any new release of anything sucks at first and only gets better with time. This idea goes with everything. Humans become more technologically advanced with time along with trial and error. It really applies to everything.
I am guessing you are just too blinded to see the reality.
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.
I believe average users will submit map problems using the app. I have already talked to multiple people I consider average users who have. So that right there defeats another one of your hallow arguments.
And the next part of this really made me laugh. You really want people to report problems from their computers? I hope that is a joke. You really are blind.
Do you not see that EVERYBODY uses their phones ALL THE TIME? People aren't going to go "Oh, it told me to make a wrong turn. Well, I will just make a mental note to remember to report that as soon as I get home! Boy, I can't wait!"
No. People never do that. Ever.
To back that up, I was at a restaurant the other day and one of my friends wanted to post a review to yelp on the iPhone app. Once he wrote it, the app told him he had to post it from a computer. Then he goes "That is ridiculous. I am not going to waste anymore time with this. I am already on the app, it makes so much more sense to just post it from here."
And he was right, it makes more sense to do it from the phone. You are oh so completely wrong.
"and we don't even know if Apple are doing some sort of quality control on this at all."
Horrible grammar.
And I find it funny that you say that as there have already been multiple stories on MacRumors and others about how Apple employees are on "lockdown" to get issues resolved. In addition, they are also actively recruiting for the maps team. Once again, for the millionth time, nothing to backup your argument.
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.
The problem with everything you just said is that you basically went against the whole idea that the more people us a program, the quicker its quality can be increased. You have anything to back that up? Because it is a known fact that when more people are using a program, more bugs will be found. And when more bugs are found, those can be fixed.
Say for example a program has 100 bugs, just for arguments sake. If you have 1 person using it, it will take some time to find all the bugs. However, if you have 1,000 people using it, it will take much less time. So if the quality of the app needed to be increased to that there were 0 bugs, it would take much less time with more people using it. Are you understanding that? Or you still lost in your own little world? The latter? Thought so.
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.
If you are going to say something like that, you better be able to explain it in detail. Because Apple makes it very easy to report problems straight from the app, the second you find a problem. But for whatever ridiculous and idiotic reason, you think it would be best if the user waited hours and hours until they got to a computer and then reported it. Ya, that makes total sense.
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...
Surprise surprise, you are uninformed once again. Apple never said they could make the perfect maps app. If you knew anything, you would know that the main force behind Apple creating their own app was to incorporate turn-by-turn, which your precious Google refused to offer.
Somehow, you missed Map Kit. RunKeeper depends on Map Kit for one. Google Maps RunKeeper = Good. Apple Maps RunKeeper = unable to map out runs and thus unusable in many areas.
That's how they "shoved it down our throats". Basically, the problem is not the Maps app itself (also, you fail to point out many Map solutions in the App Store are built over Map Kit and thus were automatically transitionned to Apple Maps with iOS 6).
I've pointed this out many times already, why do you pick that post to reply to but ignore all the other posts where I carefully explain the Map Kit conundrum ?
With this latest bit of news, it shows that Apple could have done an optional release. They didn't. I'm now irritated, thus my level of cooperation in providing feedback is now nil.
Except for the fact that the apps I have used which use Apple maps have been working perfectly. Personally, I enjoy how Apple Maps looks much cleaner overall and filled with less clutter. I think it brings in all the added detail at the right zoom point, whereas Google maps showed too many street names at once. Every time, I would end up zooming in more just to spread things out, Apple maps does that much better.
And you fail to point out that many third party map apps use their own maps. It goes both ways.
Yes, they could have waited. But I think the majority of users will enjoy turn-by-turn over street view. I for one never used street view more than once a month. I used directions multiple times a month, and now directions just got better.
And on the topic of when the right time to release is, you need to realize that the sooner you release an app, the sooner you can start really fine tuning it. Read my example above about an app with 100 bugs, that will explain it so hopefully you can understand.
with them. They're not afraid of hiring more help.