Speculation: Where did iOS 6 Maps Go Wrong? They didn’t have Cascades

Brought to my attention by Micheal @BlackBerryfan10–if we go back to 2010 we got a great preview of a TAT Cascades powered 2D/3D Map Application showing off crazy cool transitions from 2D to 3D maps achievable via the Cascades UI. See video after the break. Low and behold TAT (Now RIM Sweden) licensed the 3D Map Meshes from another Sweedish company called C3 Technologies. If their name is unfamiliar they are the acquisition made by Apple to pump up their new iOS 6 Maps with the beautiful 3D ‘Flyover’ feature. While I’m not here to discuss all the ways iOS 6 Maps generally fails as a proper mapping solution, there has been reasonable talk that the “integration” of the various purchases Apple made to create it’s final product is the problem Apple faces as it rushed to replace Google Maps on iOS 6. Does anyone remember Apples purchases of Placebase and Poly9 mapping companies? Amassing all these technologies into a complete front to back solution has caused the app to have glitches and tiny hitches that have a range of effects on the user, and generally make the old Google Maps solution more preferable. After the break I discuss why the Cascades Framework is the “frosting” Apple needed to pull off its fast transition to its own mapping solution–and why BlackBerry 10 will nail it

Check out the video above and see the power TAT was pumping into phones conceptually in 2010. While ‘Flyover’ is nice and almost makes up for lack of Google Street View, within the demo above you can see the functionality added by Cascades to C3 Technologies 3D Map Meshes. “This TAT concept seamlessly combines maps in 2D and 3D. While 2D maps are great for getting a simple overview of a place, 3D maps show you what a place actually looks like. TAT Cascades makes it possible to create maps that combine both approaches, shifting dynamically between 2D and 3D.”
While Apple may have good components, tying them together and putting the frosting on the cake is where they have faltered. TomTom is behind the maps and navigation of both BlackBerry 10 and iOS and BB1o is sporting integration from the wonderful BlackBerry Traffic developments all of this piled high with a dollop of that good ole TAT Cascades glue, er frosting:

While we’ve only heard that BlackBerry 10 will support 2D maps, maybe there are still a few secrets BlackBerrry/RIM are holding close to the chest. We’re nearing the launch of BlackBerry 10 come the end of January and I’m expecting big things from the small company. The spotlight will be on them in Q1 and they need to own it, and not hiccup over integration issues like Apple has rushing to market. Time will tell which is an ultimately better implementation.