A simple authorization mechanism should do the trick :) On Nov 9, 11:42 pm, Abhinayak Mishra <[email protected]> wrote: > hmm...interesting concept...how do you plan to keep the end user from not > just copying the premium .so and distributing it at half the price you are > selling it for? :) > > On Mon, Nov 9, 2009 at 12:41 AM, Vishal Choudhary <[email protected]>wrote: > > > > > Hi all, > > > I am creating an application that will have some basic features available > > for free and advanced features available on a premium. > > The idea is that there would be 2 .so files for various feature sets, basic > > already installed, and advanced available via download. When user purchases > > the advanced features, the .so file should get downloaded on the phone and > > user should be able to use it. > > > My queries: > > 1. Can the downloaded .so be placed in /system/lib? > > 2. If not, can it be downloaded to some other folder (say /data/advapp/), > > and if yes, how can the application refer to it? > > 3. After downloading the .so, would the system have to be restarted? > > > Thanks, > > Vishal. > > > -- > > unsubscribe: > > [email protected]<android-porting%2bunsubscr...@googlegroups.com> > > website:http://groups.google.com/group/android-porting- Hide quoted text - > > - Show quoted text -
-- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
