back

How to make a web 2.0 application

View Comments View Comments Check out this blog article #neoco #crmtweet this

Posted By Neoco

widget20.jpg
here are a few simple rules for ensuring that your Web 2.0 application is a resounding success; culminating in a £1.25bn offer from Google. I thought I’d share these with you. If you need more information you can send a cheque for £4,300 to Neoco for your own individually addressed information pack on Web 2.0.

1. Usefulness; less is more
This is the golden rule for creating a successful Web 2.0 app; always remember that less is more. Ideally your Web 2.0 app should have absolutely no point whatsoever. Sometimes a compromise is needed whereby it will vaguely useful, sometimes, to a small number of people.

2. Beta; for at least a year
All Web 2.0 apps should be in beta indefinitely. This suggests that whilst the app seems to have lots of bugs and very little point, that’s OK, because it’s only in beta – the full app is still to come.

3. AJAX; apply liberally
Ideally your Web 2.0 app should send a single line of HTML to the browser, and the rest of the app should be served via AJAX. This gives the user that slightly confusing feeling when they click a link, because they’re not quite sure if anything is actually happening (preferably nothing should happen).

4. Icons; made to look like Mac icons
Ideally you should just steal the icons straight from the Mac. If there isn’t a Mac icon to suit your needs, just use a different one. All menus should be styled with a two-tone horizontal shadow effect (again think Mac).

5. Logo; always include “2.0″
If it’s a Web 2.0 app, make sure everyone knows about this. Try to use the term Web 2.0 as many times as possible. Try to include “2.0″ in as many different places as possible; eg: “Help 2.0″.

Now get going… quickly. And if Google do buy you for £1.25bn just remember who to thank (cheques made payable to Dave).

If you get stuck making your logo, use this handy Web 2.0 logo generation utility, brought to you by “Alex P”.

blog comments powered by Disqus