The Good, The Bad and the Collaboration

The Good, The Bad and the Collaboration

Iain

You scratch my back and I’ll scratch yours

I have recently updated to iOS 6, as have most Apple users I’d imagine. I’m not one of these geeks wetting themselves over new features, and scouring the internet for product shots of the next model, I have better things to do. I have been using Apple Maps. It’s bad, make no mistake. It looks horrible, and dosent work very well. The fact a whole Tube station is missing, is quite frankly, unbelievable. This led me to question Apples decision to dismiss Google Maps in favour of their own version, and in turn, the nature of collaboration within design.

If it ain’t broke…

Google Maps works perfectly. Every iPhone user was aware of this, and as a new resident to London a few years ago the Application was invaluable, and still is. I resisted the update for as long as possible, and now I have no choice but to use Apples version of Maps. Google will at some point release Maps as an application, the sooner the better. I can only imagine they are holding off to prolong the pain for Apple. Apple are no stranger to trying to maximise control over the content and technology users have access to on their mobile devices. This is not usually a problem, given most of Apples software developed in house is almost perfect. But when Apple make a decision that is detrimental to the product and ultimately the user experience, something has gone wrong.

Apple are constantly in the process of a patent war with several companies, usually Samsung, with varying degrees of success in different countries. Although it’s clear as to why a company might seek to protect their software or technology, it also blocks the way for improvements on said technology. Open source development communities generally advance much quicker due to the vast amount of time people commit to evolving the solution. WordPress is great example of how this process is used for the greater good of everybody, although I appreciate there are huge differences between a mobile phone and a website development framework.

Dummy out of the Pram

Apple did not allow Adobe Flash Player to run on its operating system, giving some weak excuse regarding ‘Performance’. Now with iOS6, Google Maps and YouTube are gone. This is ultimately about creating a closed product, using only Apples technology. It’s almost as if Apple are hell bent on saying ‘Look what we made. We made ALL of it’. Even if that means elements of it are poor.

Too many Chefs

As a designer, I regularly feel the same emotions as Apple. I interpret a brief, come up with a solution, then design it. It’s is mine, I created it. Then comes the feedback stage. My designs usually, at some stage of the design process, get bastardised, chopped and changed at the hands of the client. Most other designers will, at some point, have had a client making design decisions for them. This can usually also involve multiple people, usually with no design experience. You get protective. And it is this feeling that I can empathise with Apple over, protecting what is mine.

But there is a line, and I think in this instance Apple should shallow their pride, kiss and make up with Google, and reintroduce Google Maps to its operating system. It’s better for everybody that way. Apple need to think of the user experience, and the consumer, before attempting to reinvent the wheel.

For those looking for a laugh, or perhaps need to see some evidence documenting just how bad Apple Maps actually is, take a look at The Amazing Maps of iOS6.

Leave a Reply

Your email address will not be published. Required fields are marked *