I Can see V13's point very clearly, As a former N900 owner, and a Former Maemo Qt developer, Now an android owner and developer,
I can already feel how much easier maintaining an android app is - compared to a C++/Qt application, and also how much more rewarding it is.

The Goal (as I understand V13 is thinking about it) - Give developers easy tools, to develop, distribute, maintain and sell applications, while rewarding them properly with income to keep them coming once more.
Once this goal is achieved, in my opinion, an OS which aims to run on multiple brands and architectures, has a good fighting chance in todays market.

Standing between that goal and the current situation are multiple aspects, let us analyze them.

1. Different form factor / onboard peripherals
2. Different CPU architecture
3. Different distribution methods.

The problem of having to take into consideration multiple form factors and added features, in the essence of peripherals, is a common one to all modern smartphone OSs. Android / Meego / And surprisingly, even apple, have this problem.
The developer must write his app to use the correct hardware, if available, and the UI needs to be able to adapt to screen size / resolution.

Different distribution methods is where so far, the N900 has been failing at, and we just don't know yet if MeeGo will address this problem with an adequate solution.
There is no doubt that the ease in which the Android market and Apple app-store allow developers to upload an application which will intern be able to be executed and used correctly on a very big quantity of end-user devices, is appealing towards developers.


As for CPU architecture :
Personally as a developer, I don't want to have to test and own 5 different devices just to be able to check if my compiled binary file really runs on all different 5 architectures. I don't have time to do it, and don't have the money to do it.
If the development IDE / SDK, allows me to select from a list of checkboxes, to which architectures I'd like to compile, and automatically upload all binaries to Ovi store, and this will really work, then we don't have a problem.
Currently in C++/Qt developers have to use #ifndef's to include/exclude hardware / distribution specific code to make things work both on Maemo and S60 and MeeGo.
If this will stop when meego is around, by supplying all the required tools via an API, this is again one step closer to allowing a batch compile to multiple architectures.

Finally, the whole thing should be easy to perform and require little time. Fast penetration with a large market of applications is necessary to succeed.