Your argument makes perfect sense. I’m not sure OQO will agree though…

It is now confirmed: Microsoft has outlined its plans for “Vistagami” — a form factor and concept virtually identical to OQO. I am still struggling to understand how OQO will compete against HP, Dell, Samsung, Toshiba, etc. unless it provides significant and attractive differentiators.

Those differentiators have to be in areas that Microsoft does not want to go, e.g. OpenDocument support. I would suggest OQO should be focused on the explosion of interest in the OpenDocument format amongst Government and Enterprise, particularly in Europe.

I’m with you! Your argument makes perfect sense from a bill of materials standpoint. Using a lighter-weight operating system would also help reduce power consumption, which is critical with such a device. Nevertheless, part of the appeal for the OQO model 01+ seems to be the ability to natively run any Windows application. I doubt that OQO will be willing to abandon this, even if that means giving up 5% of its revenues to our friends in Redmond.

One final thought from me on this!

If the Microsoft OS license makes up 5%+ of the total cost of the device — then it sure does matter. No matter how many times Microsoft and OQO kiss, the reality is that high volume manufacturers such as Samsung that have other large Microsoft engagements will always pay less for a Microsoft license than OQO.

There are now numerous options to create cross-platform stacks. These include Java, Mono, and Qt. Wouldn’t it make sense to use one of these and build a cross-platform stack?

I agree with you. A platform-agnostic model would be nice, but also much more expensive from an engineering standpoint, as Jay was quick to point out to me. In that respect, I’m not sure that the operating system matters as much as the completion of an integrated stack does.

I would suggest that while there have been a small number of innovative companies that have been successful working with Microsoft, they are the exception. When a company comes up with something really innovative, Microsoft’s lust for profits becomes all absorbing, and the small innovator gets squashed in Microsoft’s desire to build volume as quickly as possible. The Sendo example is a recent case in point.

At the very least, OQO would be wise to hedge its risk and become platform agnostic. As you’ve mentioned, the stack becomes its key selling point. The OpenDocument format could be a strategic part of this, as high volume manufacturers such as Samsung and HP are just focused on the Windows Mobile platform and the Microsoft Office format.

I’m not sure that I agree with you. Very many companies have developed quite successful businesses on top of Windows, Dell being a good example for it I believe. That being said, I agree with you that OQO will have to differentiate itself from competitors such as Dell or Samsung, and one way to do that is by offering a better user experience, which includes hardware, software and services, much like Apple is doing it today with the MacBook Pro, Mac OS X, and .Mac. My advice to Jay was to add a layer of services on top of the plain-vanilla Windows XP operating system in order to simplify the life of mobile workers, especially with respect to data synchronization. I’m not sure I managed to get my point across, but at least I tried.

Small companies that build a product strategy around Microsoft Windows end up dead companies. In order to survive versus the likes of Samsung, OQO will need to eliminate the cost of Microsoft Windows, and that means:

1. Linux
2. Strong support for OpenDocument

That would allow OQO to leverage key market opportunities in Europe and gaps that are opening in the US such as the Commonwealth of Massachusetts.

Zoho Creator has many more features than Dabble DB, but Dabble DB’s user interface is far superior for the time being. Both are excellent solutions and a matter of personal choice at this point. Down the road, I expect Dabble DB to provide a more complete feature set, while Zoho Creator will be more tightly integrated with the rest of the Zoho suite, especially Zoho Sheet. If you already use Zoho Sheet and Zoho Writer, my advice would be to use Zoho Creator as well. But if you’re trying to build a best-of-breed solution similar to my Office 2.0 setup, I would suggest that you give Dabble DB a try.

Zoho is coming out with a new release of their Creator, which is free.

How does it compare to Dabble DB?

Thanks for the kind words. Regarding the cost of my setup, I wrote an article on it three months ago. My setup evolved a little bit since then, but not significantly from a cost standpoint. The only major addition was Dabble DB, for which I am paying $25 a month. I would not trade this application for anything else though.

Prices should go down eventually.

Your blog is highly addictive. I read it daily, sometime more than once. I am totally buying the office 2.0 concept. I began unloading my files to stream load and experimenting with Writely and Zoho for spreadsheets and presentations. With my next laptop, I am going all Office 2.0. Also, how much are you paying for your setup and for what? Unlesss you run a business, it seems like all services have a single-user free version that would suit most users just fine.

Keep up the great work!