On Wednesday, November 2, 2011 9:22:29 PM UTC+2, Mark Murphy (a Commons Guy) wrote: > > On Wed, Nov 2, 2011 at 3:16 PM, Boozel <[email protected]> wrote: > > No but its not for mainstream distribution, Its for internal use. > > Um, OK. > > I > > understand the skepticism completely and see why a single "stand-alone" > app > > is the way all aps are created but if you are for example creating 10 > apps > > and they all share a lot of common functionality exactly the same it > doesnt > > make sense for me to rplicate it in each app but rather do it centrally. > > Why 10 apps instead of 1 app? Why create 10x the maintenance, 10x the > distribution headache, etc.? > Because you may only need or want a few of the apps, sort of how Microsoft doesn't lump word, powerpoint and excel into one.
> If you're sure you need 10 separate apps, why not put the common logic > in an Android library project? > Because then each app will need to be configured and managed independently. Sticking with the office analogy. Like in the screenshot below i want to create an app like one of the "Microsoft Office Tools" That configures and/or manages all the apps in the suite. <https://lh5.googleusercontent.com/-lqYRs3lC84g/TrGb61QMa2I/AAAAAAAAAVg/eSWyNl9pBhk/s400/office.jpg> > -- > Mark Murphy (a Commons Guy) > http://commonsware.com | http://github.com/commonsguy > http://commonsware.com/blog | http://twitter.com/commonsguy > > _Android Programming Tutorials_ Version 4.0 Available! > > -- 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
