Jakob Neilsen has just announced his 10 best-designed Intranets for 2010, and as always it’s a goldmine of information and advice. I haven’t yet forked out for the full report, but the summary alone offers plenty to think about.
One particular point that will raise eyebrows is the continued advocacy of separate sites for mobile devices. There is an ongoing debate about the pros and cons of such an approach, brought to the fore by Neilsen’s post last February comparing Mobile Web 2009 with Desktop Web 1998, and concluding that a separate site is best. Many of us were not convinced, and as Henny Swan argued at the time:
It also hints at repeating the mistakes of desktop web design circa 1998 where we thought the answer was to design for one browser, use proprietary technology, build text only websites for disabled users…the list goes on. So let’s not make that same mistake and instead fast forward to one of the principles of good web design that dug us out of the dark hole of 1998: progressive enhancement.
Henny described how a ‘one site fits all’ approach can be achieved using media queries, and it’s certainly a far more attractive solution than designing and maintaining separate sites.
But this all relates to websites in general, rather than specifically to Intranets, and I was interested to look closer at the suggestion of a separate mobile Intranet.
Intranet on the move?
More about mobile Intranets, and why a separate site may be justified