Content Management

Content Management is one the most important categories of software. Two years ago, Microsoft Office was the inevitable choice, with various hosting applications like Sharepoint for the enterprise. But there's been a huge amount of change in the last two years - from OpenOffice to Google Spreadsheets to Youtube.

It's now (just) possible to see what Content Management will be like in future - and it's already clear that no one is near yet.

About Content Management

The first question is, what is content?

• text (e.g. HTML, doc or xls)
• raster images (e.g. JPG, PNG)
• vector images (e.g. SVG)
• audio (e.g. mp3)
• video (e.g. mpeg)
• structured data (e.g. various XML)

The last category is really a miscellaneous bucket, which I don't expect to contain much except for niche applications. Raw XML is great for data crunching and back-end configurations, but I don't see it being used much for content - we have more specific languages (like HTML and SVG) for that.

The second question is, what is management?

• CRUD (create, read, update, delete)
• publishing
• collaboration (CRUD permissions, discussion tools)
• versioning & audit trail
• syndication (subscribing to feed)
• search
• storage (includes records management)

Web Office Suites

If you look through this list, Microsoft Office only really handles the first option. Sharepoint handles most of the rest, but that's only used in the enterprise - what about other people?

That's why you can't rule out web office suites like Google Apps - they may be very basic at CRUD, but they can be excellent at management functions 2 through 7 - and how many people really want complicated document formatting options anyway?

The most interesting content management technology is, of course, the Wiki. Wikis naturally cater for all seven management functions above. The only problem is, traditionally Wikis have been restricted to plain text and totally open permissions, but there's no reason why that couldn't change.

For example, JotSpot was (until being acquired by Google) selling a Wiki for corporate use that included HTML calendars and spreadsheets as editable pages. And I don't see why you couldn't edit other media collaboratively using a Wiki - especially vector graphics.

Ideas for a Web Office

Google has been suprisingly quiet about the future of JotSpot since acquiring it. If I'm right, their strategy will be to convert Google Apps into a Wiki suite that covers all types of content (1-6 above), and all types of management (1-7 above).

For example, Youtube could become a Wiki, including video editing capability (with permissions settings). Picasa will become a Wiki-based competitor to Photoshop. They could be packaged up with general Wiki website editing functionality, and sold to corporates (or made available to consumers, supported by ads).

To compete, Microsoft will have to cannibalize their existing Office suite, including Sharepoint. I'm still not sure they're ready for this yet.

In summary

The future of content management is Wikis, allowing management of all types of content: web pages, photos, vector diagrams and videos. It'll be based in the browser, using standard web technology like HTML, CSS, javascript and SVG. There'll be a lot more emphasis on collaboration, syndication, and search. And now the future is clear, there will be a race to achieve it - and Google has the head start.

SonyEricsson W960 versus Apple iPhone

All the recent iPhone hype has removed focus from other manufacturors plans. In most cases, it doesn't matter, because most phones are just thinner versions of the previous model.

But I'm really surprised there hasn't been more buzz about the Sony Ericsson W960, which will be released in Q4 - before the iPhone in its target markets (Europe and Asia).

Check the table below to compare features.

Feature	iPhone	W960
Touch Screen	Y	Y
Browser	Safari 3	Opera 9
Music Player	Y	Y
Video Player	Y	Y
Memory	8Gb	8Gb
Wifi	Y	Y
Connection	2.5G	3G
Camera	2 MPx	3.2 MPx
Keyboard	Virtual	Physical + handwriting recognition
Operator	AT&T	Any
Development	Ajax	Ajax + client

Note that the W960 phone will be available to all operators, developers have full access, it has a better camera, just as good a web browser, and it's 3G. Unfortunately, pricing information is not available, but it'll be interesting to see how it compares with the iPhone.

I'd also be very surprised if the W960 didn't come with MusicStation installed - which means you can subscribe to a massive library of songs, and download them directly for free - without even touching a PC!

At the very least it seems Steve Jobs was wrong about the iPhone being five years ahead of the industry ... it'll have a fight on its hands outside the US.

Ajax and the iPhone: great, but what about RSS?

So, Apple announced that the iPhone will be programmable, but only using HTML, CSS and Javascript.

Most people were pretty underwhelmed by this news - it sounds like Apple's quick fix to build a development community, and it probably is.

But this is a massive story. We will finally have a popular device whose developers will have to rely entirely on internet standards. The internet will receive another boost, as developers realise how much they can achieve - even Google Spreadsheets - and, after the kicking and screaming has subsided, I don't believe they'll want to look back to proprietary client technology.

After all, the desktop world is moving away from client applications towards the internet - and it's going to be the same on the smart phone.

Internet Apps, not Client Apps

Steve Jobs mentioned making a call and sending an email via Safari - I assume this means they'll support <a href="mailto:x@y.com">Email me</a> and <a href="callto:+112345">Call me</a> via HTML. At once, seamless integration with CRM and corporate directories will be straightforward.

Of course, this makes the decision to stick with GPRS, rather than 3G, even more strange. Download speeds will be pitiful once you're outside a Wifi connection. Surely they'll produce a 3G model soon, especially for Europe?

Offline RSS

I'd love to see offline RSS in the iPhone. If it synched your RSS feeds every time you hit a Wifi zone, and stored them locally for offline access, that would be a tremendous win.

After all, what is iTunes.com but a personalized RSS feed of music and video files? If your phone wirelessly synched up with iTunes.com, you wouldn't need to touch your PC!

And offline RSS would also allow me to synchronize with corporate files, Google's Picasa, news, and much more.

If that's not a good programming API, I don't know what is!