4 ms·
This is the first event that people will put down to a lack of Steve Jobs that I think actually might reflect that...
by peteretep 14y ago
This is the first event that people will put down to a lack of Steve Jobs that I think actually might reflect that...
- 0x006A 14y agothe decision to switch to there own maps was made while jobs was around. its also not the first time apple replaces a product with an inferior option and insists its better, final cut pro x comes to mind.
- agumonkey 14y agoDidn't they address user concerns with a .1 upgrade or was it a placebo pill ?
- 0x006A 14y agonothing really changed with .1, they added some placebo fixes, like xml import/export (except that its a new xml format that only represents trivial edits and thus is useless).
- peteretep 14y agoYes, but not the decision to ship it in its current form.
- dasil003 14y agoWould Jobs have the balls to release iOS 6 with no Maps at all for a year or more while they scramble to catch up? Those would be some huge cajones.
- bambax 14y agoJobs didn't exactly lack "cajones" but there were other approaches than just "no maps at all" - try to make the deal with Google happen; Apple has so much money it's hard to understand why they couldn't buy their way into Google Maps for another year or two - make a deal with someone else (Microsoft / Bing Maps, other map provider) while still working on their own, in-house solution It's great that Apple decided to build its own map system; the problem is they released it when it was far from ready; Apple didn't use to present half-baked products to the world.
- kristianc 14y agoYou obviously don't remember the first iPhone.
- stcredzero 14y agoI bought it. It was an MVP. The M stands for Minimal. The V stands for Viable. I still have it and note that Maps in iOS 3 over EDGE is more responsive and slicker looking than Maps in iOS 5.
- kristianc 14y agoOh, so when it suits your argument it's an MVP, when it doesn't, it's half baked. Got it.
- stcredzero 14y ago> Oh, so when it suits your argument it's an MVP, when it doesn't, it's half baked. Got it. Nice straw man and shoving words into another's mouth. When the product suits one's purpose, it's viable. When it doesn't, it's half baked. When the original iPhone was released, the bar for viable was much lower. Other smartphones were a mess, UX-wise. Just fixing the UX with a smaller feature set won over a mainstream audience. Now, the bar for viable is much higher, and it carries the expectations of a Maps application that works at least as well as Google Maps for iOS. Customer expectations change over time. Pretending that they don't for the sake of argument is either foolish or dishonest.