On Wed, Jul 20, 2011 at 8:13 PM, Indicator Veritatis <[email protected]>wrote:
> @Adam > > Did you visit the link TreKing posted? It explains that one of the > main purposes of a "Project Library" in the Android SDK is to support > a project that builds a library that can then be used to provide the > code common to both Free and Paid versions of an app. > > Of course, that still leaves a signficant, but hopefully not too heavy > burden on the programmer to factor the code so that code specific to > paid or to free versions are confined to a few small files. But this > should not be too much of a burden, especially if the programmer makes > efficient and appropriate use of Java Interfaces. > > Resources are another matter. But take a look at the link to see how > to deal with those. Yes, I believe I have said that this is what my approach was currently. (trimmed and bottom posted for nikolay ...;) It works rather well, especially as you said, if the code is organized in a way that allows differences to be in a relatively small group of files. Standard design patterns and development best practices are of course useful here. -- 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
