> This is what lawyers and contracts are for. If a user emails me with a legit bug report, they seem to be pleased with a reply including an APK to test. Somehow I don't think they'd appreciate a contract nearly as much. And is the lawyer really going to try to enforce things all over the world, or would the contract be for USA only and cut out all those volunteer translators in other countries?
> you can sign test versions of the app with your debug keystore > which will have an expiration date typically <= 1 year This doesn't prevent it from being installed, just prevents you from releasing an update for it. Also worth nothing, that if a beta tester or even pirate is using an app signed with your own key, they can go to the Market and buy it and install the update and now they're legit without hassel. But if they're using a APK signed with a different key (debug key, or signed by the pirate cracker) then they get a "Package signed incorrectly" error and have to uninstall before they can get the Market version. > Now, I am looking for a professional way for deal with the problem. > As this must be a very common scenario for every developer. There must > be a good solution for this problem. My needs, which may differ other developers: 1) Aside from Google/Amazon I accept paypal directly and have a fair amount (> 2,000) of users that have gone that route. This is a utility app where updates are very important to users. Giving them the APK just once isn't sufficient, they need updates. Only the Market isn't a good solution as some countries still don't have it and many people don't have credit cards or trust Google Checkout. 2) Beta testers and translators, some of which are more trustworthy than others. Before I implemented a proper system one of my non-copy- protected betas was leaked by a translator. I learned my lesson. 3) Gift to previous Google Market users who have switch accounts, got a secondary Chinese tablet type device without the Market, etc 4) Gift to App reviewers, friends, other developers, etc For a long time I handled this with mailing lists to send the APK and updates (with no copy protection) to everyone. (One list for stable and one for beta). This is a headache and does not scale and you get so many emails lost in spam or bounced or whatever. (But it takes very little effort to setup, so you might consider it for that reason. Just replace it before you have several hundred people on the list) I ended up rolling my own setup, which I'm quite pleased with. When I add a user (either beta user or stable user), my server emails them with: Their authorized email address Their authorization code A URL that will always download the latest APK for said app (stable or beta, depending on user type) They download the APK and it prompts them for their email and authorization code, they hit submit and it verifies from my server, then unlocks the app. The app can license check, using a system very similar to LVL (so I can reuse my LVL code), over http. Server controls how many devices the users are licensed for, and I can increase these if I have a trusted beta tester with lots of devices or decrease/revoke if I see someone leaked their credentials. The app can also check for updates by itself and download the latest version and leave a notification for the user to install it. My setup isn't polished enough for people that are not me to use right now. But is there interest in something like this? Would developers pay for a hosted service like this? (I know I would've paid for one when I was looking, but I couldn't find anything that met my needs. AndroidPit will charge you to gift an app and has nothing for betas. AndroidLicenser doesn't do updates or betas and is limited to one license per device) -Kevin On Jun 22, 12:42 am, yogesh bansal <[email protected]> wrote: > Hi, > > I am newbie android app developer. I am confused, how to deliver the > APK file to customer for testing. Let suppose, if i give the apk file > directly to customer for testing. Then the purpose of the customer is > solved. Now he has the apk file with him and He can use it freely and > after that he can refuse to pay the money. It is possible , i have to > deliver apk file to customer every day for testing . Once the > application is finalized, he can refuse to pay. As I have a consent > with the customer, that he has all the right of the application and > code, so i cannot upload the application in the android market also. I > know that , i can put some kind of check inside the code to restrict > the usage. But i feel that won't be a good approach and also not > professional solution. > > Now, I am looking for a professional way for deal with the problem. > As this must be a very common scenario for every developer. There must > be a good solution for this problem. > > Please guide me on this problem > > Thanks > Yogesh Bansal -- 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
