4 ms·
Overall an excellent thesis. One quibble, though, with this: "Some software development just simply works better with a continuous development process. Maps is
by Terretta 14y ago
Overall an excellent thesis.
One quibble, though, with this: "Some software development just simply works better with a continuous development process. Maps is a really notable example, all of the data lives outside the product and as the data improves, the product seems to magically improve as well... And this is where Apple is struggling, by viewing software as huge steps with small shuffles in between, they struggle in cases where software development works best as a continuous reasonable walk."
I happened to be traveling in Italy during the last week of iOS 6 beta and the first two weeks of iOS 6 release, and was amazed to see the sudden dramatic improvement in maps on an almost daily basis during that trip. At the start of the trip, we still preferred the original maps on iOS 5, but by the end of the trip, the iOS 6 maps felt superior in most ways.
Apple was clearly updating both the "cloud" map data and the map functionality without a point release to iOS itself, and iterating incredibly fast. Seems to me if the "new maps" journalism had been delayed about three more weeks after iOS 6's release, the "first" impressions would have been markedly improved.
I also believe, based on the types of things that changed, that the iteration was driven by real world mass usage data that Apple just couldn't get from the beta or GM install base who use iPhones differently.
- bane 14y agoYeah, I agree. I think Apple is moving towards this kind of development, but it's just not in their present DNA. I wonder how much of the rapid map improvements were the very public bad press and the apology by the CEO putting a laser focus on the problem vs. something that would have happened organically? Looking at the glacial pace of Siri improvement and the low prioritizing of the iTunes recommendation engine, I can't help but wonder. In other words, I don't think Apple really wants to move to a more continuous software development model, but market forces are simply forcing it to do so. It is surprising that they aren't investing more of their piles of cash into expanding and improving their software development practices.
- Terretta 14y ago> I wonder how much of the rapid map improvements were the very public bad press and the apology by the CEO putting a laser focus on the problem vs. something that would have happened organically? The iterations, things like building outlines, or on the iPad, 3D building textures for historic Rome, could not possibly have been produced on short notice. I believe iOS 6 Maps was simply a month behind schedule, and iOS 6 was launched before Maps was ready, with data and features continuing to release until they hit their deliverable. After that additional three weeks, Maps seemed to stabilize into incremental improvements rather than the leaps and strides made during in the three weeks after iOS 6 release. > It is surprising that they aren't investing more of their piles of cash into expanding and improving their software development practices. My perception is Apple has a different dev model of sticking with comparatively small dev teams in an effort to keep product lean, focus tight, and quality and polish high. I'm not sure what the result would be if they expanded teams. Some research suggests both quality and output might actually drop.