Changes

The Sugar Platform cannot grow endlessly and components like Qt or OO4Kids are (at least at present) out of Sugar Platform list. But activities can still use such dependencies by installing them from native packaging systems without bundling binaries. See [[Documentation_Team/Services/Native_packages_usage|Native packages usage]] to know how to utilize native packages in your activity or service.

The Sugar Platform cannot grow endlessly and components like Qt or OO4Kids are (at least at present) out of Sugar Platform list. But activities can still use such dependencies by installing them from native packaging systems without bundling binaries. See [[Documentation_Team/Services/Native_packages_usage|Native packages usage]] to know how to utilize native packages in your activity or service.

=== Service developers ===

=== All sugar developers ===

Any developer could get benefits from 0install [http://0install.net/goals.html features] to:

Services are intended to decentralize sugar development process e.g. if you have some idea in mind, you can start pushing it through entirely release queue to get it in the next(maybe not nearest) Sucrose release. The core issue here is that there are only YES and NO answers to inclusion your feature to Sucrose, so if there is 51% against and 49% for inclusion, feature could be rejected/postponed. Services make development process more flexible and let developer benefit 49% of users.

* provide libraries or applications that are not intended to be included to [[0.86/Platform_Components|Sugar Platform]]

* provide libraries or applications that are not intended to be included to [[0.86/Platform_Components|Sugar Platform]]

** could be used by few activities

** could be used by few activities