Shared publicly  - 
Among other things I'll try to contribute a bit to "apps in Ubuntu" next cycle and wrote up some thoughts earlier:
Jono blogged about the importance of application developers to Ubuntu earlier and I wanted to echo some thoughts and add some of my own. I have been in the Ubuntu Developer camp for most of Ubuntu&#39...
Fabián Rodríguez's profile photoCaleb Callaway's profile photo
This may be reading comprehension fail on my part, but I'm not seeing a clear strategy for maintaining stable deployment targets for apps and applications, which I think will be critical to such an ecosystem's success. I can personally attest that stable deployment targets are a hard requirement for the average application developer, and I expect the same is true of app developers as well.

As a concrete example, I think a successful ecosystem must not have any concept of package dependencies. I expect app developers won't be satisfied with anything but a single, implied dependency on the app framework itself.

Some recent remarks by Miguel de Icaza seem relevant:
I also don't see anything about publishing such software under free licenses while building a sustainable business. Disappointing.
+Fabián Rodríguez Do you have examples of how that goal might be accomplished? I've yet to see a compelling revenue model. Ad-supported would probably just annoy the users (and the license would allow them to remove it), and selling support services doesn't seem very viable for apps.

I generally take the attitude that reputation is the currency in FOSS software--producing high quality FOSS software increases the reputation of the author(s). In this model, a Ubuntu app ecosystem could be viewed as a means of promoting a brand, either personal or corporate.

A reputation model would require careful moderation to prevent apps that only promoted a brand without delivering value to the user, though.
Add a comment...