I've been pretty disappointed in the library projects. They are pretty much broken IMO. Although I have set it up there way, a lot of the application is resources, which don't seem to be picked up properly. Then you have the problem of providers with the same authority in two different packages! Not to mention having no end of issue when UI code is stored in a lib.
Its pretty crazy how limited the library projects actually are. However, I have set that up, but I'm still having to maintain two versions on the fly. At the moment I'm being very good about making a change across both but we both know that can't last :) In the mean time, I'm simply working to extract the logic of the app(s) and move it into the lib. - Brill Pappin On Dec 7, 10:39 am, Emanuel Moecklin <1gravity...@gmail.com> wrote: > Hi YuviDroid > > To maintain several versions of the same app with minimum redundancy > and without any refactoring you can use library > projects:http://developer.android.com/guide/developing/eclipse-adt.html#librar... > (link if you are working with Eclipse). > Since the September update of the SDK it's also possible to have > library projects depending on other library projects. > > I'm maintaining three versions of one app and two more versions of an > app based on the first app with two Android library projects, one > depending on the other one, and five Android projects with almost no > redundancy (app icon, manifest, some assets but all these files would > differ from version to version of the app anyway). Seven projects > sounds like a lot but five of them are really just "skeletons", the > real code is within the two library projects. Google really did a good > job here (although I would appreciate if assets could be stored in > library projects too;-). > > Emanuel Moecklin > 1gravity LLC > > On Dec 7, 4:03 am, YuviDroid <yuvidr...@gmail.com> wrote: > > > > > To maintain two versions of the app, I personally simply use a static > > boolean "RELEASE_DEMO", that I set to true when releasing the demo one. > > It's just a little pain that you have to rename the packages, and eventually > > some code if it references the package in some hard-coded way. But at least > > I don't have two completely separate applications in which case I would have > > to keep copying/pasting every fix/modification/feature/etc... > > > Yuvi > > > On Tue, Dec 7, 2010 at 3:50 AM, Brill Pappin <br...@pappin.ca> wrote: > > > I've been thinking of trying that. It can only popup once to let the > > > user know because it would be a real pain for them if it popped up > > > every time the keyboard did :) > > > > However they would be able to click directly to download it or maybe > > > tell it to remind them rather than just going away for ever. > > > If you combine that with TreKing's idea of a button in the settings, > > > and you have a pretty good chance that the user will know they have > > > the option. > > > > I must say, I'm happy that the users will have a chance to try it free > > > first, because its the kind of thing that there are many poor > > > implementations of. Now I have to figure out how to maintain two > > > versions of the app, as the library system seems to be very broken! > > > > - Brill Pappin > > > > On Dec 3, 5:52 pm, YuviDroid <yuvidr...@gmail.com> wrote: > > > > You could push an update to the free version, and then in its app > > > > description advertise the paid version. In this way users who will want > > > to > > > > update their free-installed version will see the promo text in the > > > market. > > > > (although they might use the "Update all" button and not see the new > > > > description...). > > > > > I've never written an input-method, but if it's possible to show a > > > > dialog > > > > (or launch an activity) you could show a one time promotion of the paid > > > > version when your input method gets opened. Mmm....does it make sense? > > > > :P > > > > > Yuvi > > > > > On Fri, Dec 3, 2010 at 11:12 PM, Brill Pappin <br...@pappin.ca> wrote: > > > > > Actually, my question was not about a separate app, but more along the > > > > > lines of how you tell the user they can upgrade. What ways work and > > > > > are unobtrusive and what ways don't. > > > > > > - Brill Pappin > > > > > > On Dec 2, 5:46 pm, Leon Moreyn-Android Development > > > > > <lmor...@earthcam.com> wrote: > > > > > > pretty much thats the general method being used. One thing to > > > consider > > > > > > is unpublishing the app and releasing a paid version in its place. > > > But > > > > > > users may find that kinda a slap in the face. I would say do as your > > > > > > doing, add features to the app and call it app Plus and charge money > > > > > > for it. Remember though those feature need to be worth the price you > > > > > > apply to the app though. What you can do is remove features in an > > > > > > update to your free app and keep them in your paid version. > > > > > > > On Dec 2, 3:42 pm, Brill Pappin <br...@pappin.ca> wrote: > > > > > > > > I've got a situation a lot of us do, where I have released a free > > > > > > > version and now need to make a Paid version of the same app. > > > > > > > > As those who have tried will know, you can't change an app from > > > Free > > > > > > > to Paid (a silly feature of the Market). > > > > > > > > So, what I'm planning to do is release a "Plus" version that has > > > more > > > > > > > features. > > > > > > > > What are others doing to help direct users to their paid versions > > > from > > > > > > > their Free versions? > > > > > > > I'n my case its an input method, so I have to be careful about how > > > I > > > > > > > tell the user about the paid version with more features. > > > > > > > > Comments? > > > > > > > > - Brill Pappin > > > > > > -- > > > > > You received this message because you are subscribed to the Google > > > > > Groups "Android Developers" group. > > > > > To post to this group, send email to > > > android-developers@googlegroups.com > > > > > To unsubscribe from this group, send email to > > > > > android-developers+unsubscr...@googlegroups.com<android-developers%2Bunsubs > > > > > cr...@googlegroups.com><android-developers%2Bunsubs > > > cr...@googlegroups.com> > > > > > For more options, visit this group at > > > > >http://groups.google.com/group/android-developers?hl=en > > > > > -- > > > > YuviDroid > > > > Check out Launch-X <http://android.yuvalsharon.net/launchx.php> (a > > > widget to > > > > quickly access your favorite apps and contacts!) > > >http://android.yuvalsharon.net > > > > -- > > > You received this message because you are subscribed to the Google > > > Groups "Android Developers" group. > > > To post to this group, send email to android-developers@googlegroups.com > > > To unsubscribe from this group, send email to > > > android-developers+unsubscr...@googlegroups.com<android-developers%2Bunsubs > > > cr...@googlegroups.com> > > > For more options, visit this group at > > >http://groups.google.com/group/android-developers?hl=en > > > -- > > YuviDroid > > Check out Launch-X <http://android.yuvalsharon.net/launchx.php> (a widget to > > quickly access your favorite apps and > > contacts!)http://android.yuvalsharon.net -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
