web 2.0

iPhone OS 3.0: The lesson of not doing every basic thing first

iphone-os-3

Last week Apple released the much anticipated update to it’s iPhone operating system. Finally bringing many of the features most phone providers would have thought completely necessary in a modern smart phone: MMS, Video capture, Cut, copy, paste, Memo recorder, Background IM applications.

The Apple website lauded these new features as exciting developments, yet they can be found on most current Nokia, Sony Ericson, Samsung, LG and HTC handsets.

It’s taken two years to get these features on the iPhone – with many saying 3.0 is what it should have had when it launched. Yet everywhere I look i see iPhones, it’s easily the favoured handset amongst my friends – with the previously unconvinced now benefiting from their purchase of the new iPhone 3G S.

So did this lack of key features make a difference in the beginning, did it limit the success – no. The iPhone was so far ahead of the competition in other areas that people felt happy to live without these must-have features. This approach to not including everything people expect underlines a key principle for the internet age

Prioritise your killer features to bring instant success and don’t be afraid to add the perceived must-have basics later.

Avoiding the mythical phase 2 or phase 3

How many times have you heard – “That’s a cool idea, but lets put into phase 2″ – it’s an admission, a lack of confidence or ambition – and a fast track to mediocrity.

It happens like this, new service developments, shops & services start with hygiene factors. The team worry about doing the basics well and spend most of the budget doing these. Invariably things don’t go to plan and the pot for all the innovative extras gets smaller and smaller. The site or service launches, and it immediately fails to get traction, the audience figures grow much slower than expected, feedback isn’t a positive as expected which further pressures their development budget. This leads to a review of the project, a postponement of phase 2 – and a belief the service idea doesn’t work or the core idea was failed.

The next time your team think about delaying an exciting and innovative idea to phase 2 – ask yourself this – which of our supposed must-have features can we delay instead?

Delivering on your ambition

If your ambition is to build a better X – and let’s face it just about every project starts that way – don’t start by copying the competition and talking about doing the hygiene first. If you’re not innovating or doing something noticeable, why should people change their existing behaviour. Playing catch up with your competition is hard. Start from a positive position and force them to try and catch you. And remember if hygiene is easy it will be easy to add later.

If you take a look back over the myriad of web 2.0-like developments we’ve seen over the last few years. The ones that succeed are the ones that get their new ideas out there quickly, claiming their space with a bright new idea and then adding new features as their audience grows and helps them understand what makes sense.

So be brave, implement the things that differentiate first, then add the basics over time. If you talk about doing a phase 2 – make sure you’re audience is so excited they want a phase 2 and you then deliver on it.

Tags: , , ,

0 comments Add This

Three cheers for DDA compliance.

Google have recently passed comment on the whole Web 2.0 phenomenon; surely the very Earth itself must tremble with the weight of wisdom being imparted. No? Oh well.

So what have they said about Web 2.0? Basically it boils down to this: Make sure JavaScript is not the only route to your content. This is simple repetition of what they have been saying all along really.

However, before I get accused of Google bashing, I will say that this article includes some very sound advice, especially for UK sites. At the very core of Google’s message is "build a site to be accessible", and this is so relevant in the UK considering DDA compliance. The Disability Discrimination Act states that:

a service provider has to take reasonable steps to change a practice which makes it unreasonably difficult for disabled people to make use of its services.

It goes on to say:

What services are affected by the Disability Discrimination Act? An airline company provides a flight reservation and booking service to the public on its website. This is a provision of a service and is subject to the act.

So, if your website provides a service (is providing information on your services considered a service?) then it must be accessible to all.

The DDA is the best thing to ever happen to search. Finally large, sluggish corporations are taking notice. Following years of advice from their SEO agencies, asking them to change this and that on their sites, suddenly the threat of a good old fashioned court case, bought by the disabled, in a high-profile media circus, suddenly makes them sit up and pay attention. Well, it would, wouldn’t it?

JavaScript is evaporating before our very eyes. Images without ALT text are suddenly growing the stuff overnight. SEO consultancy is getting easier; if your recommendations are backed up by confirmation from Google and the weight of legislation, they tend to be taken seriously.

However, with the cancerous spread of Web 2.0 (remind me to post my thoughts on this detestable phrase at some point) we are seeing more and more JavaScript being introduced into sites in the form of Ajax-driven, trendy front-ends. Don’t get me wrong, Ajax has its place and if implemented well and with accessibility in mind, it can be a fantastic addition to a site. Google Maps is a perfect example of this; disable JavaScript and you are presented with a plain HTML alternative. The experience is no way near as slick, but the service is provided and the information is available.

However, so many of these Web 2.0 sites are dying a death because the people commissioning them have been won-over by a flashy design and some exciting functionality, without giving a second though to either the disabled or their own search engine performance. Search engines take one sniff and turn their noses up in disgust at the perceived lack of content.

If your site is DDA compliant, then the chances are it is pretty accessible to search engines too.

Tags: , , , ,

0 comments Share