One architectural problem with Android is that Intents are overloaded with many different purposes - they carry data, specify actions, launch choosers, kick off services, and much more. On top of that, Android allows most objects, including Intents, to be specified either dynamically in Java or statically in XML or a mixture of both. This means there are 100 ways to do everything and no one, true way to do anything. System architects love creating power and flexibility. Application builders just want to get their CRM workflows running. But Android is new and still evolving so a middle ground will be found.
-- 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
