Two examples of potentially disastrous "upgrades" --
In iOS 6 the maps functionality took a major step backwards. Just shipped yesterday so we're still figuring out how bad it is. Maps are critical functionality for mobile users. Why it happened, no one knows. Could be that Google pulled out on their own. They might not come back, hoping that maps will be a feature advantage for their Android phones. Remember these companies have been suing each other over patent issues.
I don't use Twitter clients, but I understand that their iPad app, acquired from Loren Brichter, was an exemplary iPad app. The new app apparently pales in comparison. Again, we don't know how this came to be. But it may be indicative of a similar kind of problem for Twitter.
Ashton-Tate is prior art for self-destructive upgrades. They had a theory that you could ship a new version of a product, in this case dBASE, without anyone in the company actually using it. It didn't work. They ended up selling out to a much smaller competitor after this upgrade ruined the company.
So the stakes can be very high.
I learned this one in 1984, when we shipped ThinkTank for the Mac.
People thought we had removed features from ThinkTank, because they had used the Apple II or IBM PC versions. In fact this was a completely new codebase, and we shipped early because there was a lack of software on the Mac. So it didn't have a lot of the features of the earlier product. No matter, the users were outraged by this. They thought they had bought a better computer, and here was the product with less features. We totally didn't anticipate this, because from our point of view it was a major accomplishment to get something out at all.
As the story goes, the customer is always right. We quickly came out with a new release that added all the features that were in the other versions.
I was concerned with the maps upgrade so I didn't bother upgrading today. I should be getting my iPhone 5 delivered tomorrow so I'll see for myself. My fiance upgraded her phone today and the maps app looks ok so far. I was worried that there wasn't walk directions, but it's in there, just kinda hidden.
another observation. If you've used the [x] button to cause the OPML Editor to be sent to the task bar on Windows, the Green Button shows, but the app doesn't come to the front when it's clicked. It does open the comments workspace, but doesn't present.
this is on a windows 2008 server set to run like a client machine using Chrome [Version 22.0.1229.64 beta-m].
it's also quite possible that this is an unavoidable side-effect of the windows taskbar
Here's my 2 cents: Six Apart's "upgrade" to Movable Type 3.0 proved disasterousÐto them.
Observation: em-dashes break. I guess I should be using html code for them -- like this.
WordPress took the opportunity to welcome users with open arms.
Looks more like four examples to me!
How about a test comment?!
I upgraded to iOS 6 yesterday and used the new Maps application and its turn by turn feature to get to and from dinner (a 45 minute drive each way).
My experience with the app was great. I enjoy its visual interface and 3D perspective. In many ways it was an improvement over the Garmin I've been using for the past 3 years.
I think the issue with Maps will be entirely data related. I'm sure there will be holes but I expect things to get resolved quickly on the server side.
The app claims to be powered by TomTom's dataset and hundreds of other smaller companies for world coverage. I bet international mapping will be hit the hardest early on.