Apple’s Maps App Starts Showing Signs of Improvement

Status
Not open for further replies.
This is just like SiRi... it barely worked when they released it. Now it works "decently enough".

This kind-of software improves with use. Just give it time.
 
[citation][nom]frombehind[/nom]This is just like SiRi... it barely worked when they released it. Now it works "decently enough".This kind-of software improves with use. Just give it time.[/citation]
apple apologetics at its finest
 
[citation][nom]frombehind[/nom]This is just like SiRi... it barely worked when they released it. Now it works "decently enough".This kind-of software improves with use. Just give it time.[/citation]
The problem is they had something that worked perfectly fine. What people are complaining about is the releasing of an unfinished project. People were pretty much used as beta testers on what was supposed to be a "new feature" in iOS6.
 
Graphics improvements are far less important than improving the get to where you need to go problem. Kudos for improving Apple, but you have a helluva long way to go and you're doing it the way that you and others accuse Android of doing, by using your sheep as guinea pigs.
 
[citation][nom]nokz[/nom]The problem is they had something that worked perfectly fine. What people are complaining about is the releasing of an unfinished project. People were pretty much used as beta testers on what was supposed to be a "new feature" in iOS6.[/citation]
Umm, Microsoft has been doing this since Windows 95. Adobe and Oracle (Java) have been for a few years now, and apparently Apple has just caught on.
No, it isn't right.
But the simple truth at the end of the day is that its so much cheaper to fire your entire testing department and just patch bugs as your users report them.
 
But regardless, Ultimately apple had to do this... if they hadn't and Google decided to be really competitive and cut off map support to Apple phones out of the blue, Apple would have been SCREWED. They prolly could have extorted them for some exorbitant sum of money to keep map support until apple worked out their own map app.
 
[citation][nom]kinggremlin[/nom]So when is this site going to change its name to "Tom's Cellphone?"[/citation]

After they completely abandon the broad computer hardware benchmarking that made them famous... Oh wait that already happened. Welcome to Tom's Cellphone, Est. 2010
 
3 developers already died from exhaustion, one other jumped off the roof of the building. Police was called in when unrest broke out in the kitchen area after the RedBull supply ran out.
 
Version 1.0 of a product a company hasn't tried before that has some issues? Never heard of this before, must be unique to Apple.
 
[citation][nom]hyperanthripoid[/nom]Of course it is, It would be harder to show signs of un-improvement.[/citation]


I've been using it for a few weeks with an iPhone 4, and as of Saturday a 5, and have not noticed any problems in the Green Bay, WI area.

But I suppose not seeing a problem with something Apple made makes me a fanboy.
 
[citation][nom]frombehind[/nom]This is just like SiRi... it barely worked when they released it. Now it works "decently enough".This kind-of software improves with use. Just give it time.[/citation]

Point is it shouldn't have barely worked. It looks like Apple didn't even Alpha test it. It basically was the "It compiles so we'll release it" type of software. Given Apples large software development base this should have been much more refined before release.

Remember Apple's thing has always been polished, smooth, well functioning software.
Clearly this wasn't.
 
frombehind: But regardless, Ultimately apple had to do this... if they hadn't and Google decided to be really competitive and cut off map support to Apple phones out of the blue, Apple would have been SCREWED. They prolly could have extorted them for some exorbitant sum of money to keep map support until apple worked out their own map app.
------------

Actually, They still had a year or so left on their contract with Google maps, Apple themselves cut it prematurely.
 
[citation][nom]luciferano[/nom]Graphics improvements are far less important than improving the get to where you need to go problem. Kudos for improving Apple, but you have a helluva long way to go and you're doing it the way that you and others accuse Android of doing, by using your sheep as guinea pigs.[/citation]

Do you have an iOS device by which to compare, or are you reading a couple of over-blown internet articles and making your own assertions? The one percent are the ones complaining, and even then the majority of what I've read has been trivial things, like showing a monument two hundred feet south-west of where it actually is - the usability of the app hasn't suffered for many, and if for some reason it had for you, you had plenty of options.

Apple doing this is akin to Microsoft no longer bundling Java with it's Operating Systems. And to be honest, from a business case, what sounds better: avoiding paying royalties on each and every of the tens of millions of the new product you're about to launch, or having a couple stories mock a stupid app you put out, knowing full well that it's not that big of a deal?

Plenty users, myself included, have had absolutely zero problems, and as some have pointed out if anything the maps load faster, because of the way they are rendered. If having a hiccup in an app makes you dislike a company or it's products THAT much, even when alternatives are offered, then hey, return your $600 rare smartphone. Somebody else will buy it.

BRB need to go be an Apple fanboy again. Because that's what I am, for having the Maps app work correctly, right?
 
Status
Not open for further replies.