Why I Bet My Company on Qt and MeeGo

With all the entrenched competition from Android, IOS, and Palm/WebOS, Qt/MeeGo certainly has to play catch-up on the mobile phone platform. However, the future is going to be filled with a wide and ever-expanding universe of devices beyond phones where Qt/MeeGo's better suited than its phone-centric rivals -- as a development environment and, ultimately, in deployed performance and experience, service and maintainability. The future is about lots of diverse, interconnected devices where no one vendor can control it, and Qt/MeeGo is better positioned to thrive in that kind of an ecosystem.

I'll compare and contrast Qt/MeeGo and competitive OSes from a feature and business model perspective, ultimately showing that Qt/MeeGo is flexibility and broad device support clearly make it the platform of choice for the widest range of applications and devices beyond smart phones -- not just tablets, but ovens, cars, thermostats, doorknobs -- you name it! As an independent software company developing software for multiple clients in parallel, Qt/MeeGo lets us reuse code, develop for multiple platforms simultaneously, shift developers between projects and clients efficiently, and deliver the highest quality code to our clients and their customers.

I'll finish with an open discussion about current and planned Qt/MeeGo development projects and how to optimize them for even greater success. (This can continue as a follow-on Birds-of-A-Feather meeting.)

Some specific things we'll cover:

- Features of Qt/MeeGo vs. competitive OSes -- from a feature perspective
- Features of Qt/MeeGo vs. competitive OSes -- from a business model perspective
- How my company, and my company's clients, execute business initiatives leveraging Qt and MeeGo
- My rationale in picking Qt and MeeGo
- What are others working on? What's the optimal way to develop with Qt and MeeGo?