Because APIs that we integrate in the platform must be forever maintained and cannot be changed ever. This adds burden to the Android team and it's less flexible for you because we need to maintain backward compatibility. It also adds bloat to the platform. A good example of a widget that should never have been in the platform is the sliding drawer. It made sense when we added it because our UI was using it, and developers were asking for it, but a couple of years later it is barely used anymore. It should have been in an external library.
On Mon, Jul 18, 2011 at 7:16 AM, TreKing <[email protected]> wrote: > On Mon, Jul 18, 2011 at 4:31 AM, Romain Guy <[email protected]> wrote: > >> It's also for cool APIs that can be useful to all app developers but that >> we don't necessarily want to add to the platform. > > > Out of curiosity, why would you not want to add "cool APIs that can be > useful to all app developers" to the platform? > > > ------------------------------------------------------------------------------------------------- > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > transit tracking app for Android-powered devices > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- Romain Guy Android framework engineer [email protected] -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
