Eclipse works for signing your apps just fine. As for Piracy, I guess, don't worry for it right away. May be after a few updates, or when your app gets very very popular, and people would be tempted to pirate it. Till then, I guess you are safe.
-Kumar Bibek http://techdroid.kbeanie.com On Tue, Oct 5, 2010 at 11:31 PM, Nathan <[email protected]> wrote: > 1) Piracy: Don't know how worried you should be yet. Unlike some here, > I am not of the opinion that piracy will actually increase my sales, > nor do I believe that 0% of the freeloaders would ever pay for my app. > But despite this philosophical leaning, I've never gotten around to > doing LVL, proguard or other antipiracy steps. I've just been too busy > improving my app. > > 2). Read up on the Android Library Project. I haven't used it fully > yet, but it could be helpful. > > 3). Package names have to be different for two listings in the market. > That way they won't conflict, and you won't have to remove the demo > version first. Preferences won't transfer by themselves; someone else > here may know more about that. > > 4) Don't think it matters. Use the keytool. > > > > On Oct 5, 9:44 am, Joel Duggan <[email protected]> wrote: > > So I'm ready to release my first app. It's a live wallpaper (getting my > > feet wet with something simple) and I need some guidance. > > > > I have a few questions that I'd really like some answers to. > > > > 1) Piracy. How worried should I be? I could use the Google LVL stuff > but > > I've read that it's basically useless unless you also use something like > > Proguard. My app only has a couple of classes which likely wouldn't be > > affected by proguard because they're referenced in the manifest. Should > I > > bother with anything at all? > > > > 2) Demo vs. Full. I'd like to release a Demo/Lite version plus a full > > version. The lite would basically change the name of the app and force a > > few preferences to disabled so that the user sees the preferences and > > "wants" the full version. What is the best way to manage this, from > within > > Eclipse preferably? > > > > 3) How do I manage things so that the user can upgrade simply without > > having to remove the demo version? From the things I've read it sounds > like > > there can be a collision with a name or key or something (package name > > perhaps) that requires the user to remove the demo version before the > full > > can be installed. > > > > 4) Should I just use the keytool to get a key set or should I use > something > > more reputable? Does it matter? > > > > Any help/advice would be much appreciated. > > > > Joel > > -- > 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]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en -- Kumar Bibek Mobile : +91-9663304186 Mail : [email protected] -- 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
