On Mon, Mar 29, 2010 at 10:19 AM, Mark Murphy <[email protected]>wrote:
> Creating Android JARs is fairly easy...so long as all you want to do is > ship Java code. If your Java code needs resources or assets, or offers > up activities or services, then you have to ship a JAR plus a whole > bunch of other stuff. And the person reusing your JAR would need to know > about all that other stuff, find it, download it into the right spots, > etc. The only way that is somewhat convenient for the developers is to > package this stuff into separate APKs...which is inconvenient for the > users. > > IMHO, that's one of the reasons why we don't have a robust collection of > third-party widgets or other libraries. There are few recipes for > creating such things, no standards or conventions for how to consume > them, and no home for them to live. At least, I am not aware of much in > this area -- please correct me if I've missed something. > Sounds like intents could solve some of the problems if apps and widgets are developed with reusability in mind. -- Ning -- 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 To unsubscribe, reply using "remove me" as the subject.
