One abstract that separates beatific developers from enthusiastic developers is act with their community. One enthusiastic artefact to move hardcore users and simultaneously meliorate your creation is by substance beta APKs for download and feedback. Unfortunately, whatever well-being developers are existence ripped soured as a result.
Earlier this period we saw . That’s right: someone meet took the beta APK, subscribed it with their possess info, and uploaded it direct to Android Market.
That’s despicable. Months of hornlike impact compromised in a concern of minutes. Isn’t there a artefact to kibosh this? Not at the moment, but I’ve got digit suggestions for Google and one for developers:
Unpublishable Package Names
Every azygos Android Application or Game has something titled a “package name”. It’s a unequalled ordered of characters that identifies an app. Because Android Market identifies apps and games as collection names, you could modify easily modify the denomination of your app in an update.
For example, the collection study for : holograph to the lowermost mitt and you’ll wager it (com.google.android.apps.maps).
Unsigned APKs crapper be easily jacked by rapscallion developers, they meet hit to clew it themselves and upload to their mart account. But what if the actual developer ALREADY signs it? You’ve ease got the aforementioned difficulty with a whatever key details:
- If the beta app has never been launched on Android Market, Google module hit no achievement of it, so the prototypal mortal to upload it to Android Market with that collection study module intend “credit” for actuation with that collection name.
- Once the app is taken and publicised to market, the felon won’t be healthy to update the app because they won’t be healthy to clew it with the comely password. Plus the REAL developer module be using a newborn collection name. But at this point, the alteration has been done.
After a developer has already launched their app or mettlesome on the market, the venture goes downbound dramatically: as daylong as they’ve subscribed the app and provide it the aforementioned collection name, nobody crapper move it and publicize to mart themselves because Google module refer that this collection study is already owned.
But today you’ve got a newborn problem. If you’ve got hardcore users they’ll probable poverty BOTH apps installed: the actual one and the beta. The beta module overwrite the authorised promulgation UNLESS you’ve got assorted collection names. So… someone could continually verify the differently titled beta and start on Android Market as their own, unless developers are actuation Beta’s on Android Market and countersign protecting them. Which, become to conceive of it, isn’t a intense idea.
So after this unbelievably daylong explanation, this is one unbelievably cushy artefact Google could preclude rapscallion developers from concealing subscribed beta apps and business to mart as their own: unpublishable collection names. Choose a primary “safe word” much as “unpubbed” or “beta” or “private” and if the collection study begins with that chosen word, Google module disallow upload of the app or mettlesome to Android Market. Easy peasy.
Reserved Package Names
Perhaps an modify easier choice would be to earmark developers to index into their accounts and ordered collection obloquy that they’d aforementioned to ingest in the future. So for example, I could inform Google I’ve got this newborn app I’m employed on and the collection study is “meaningoflife.phandroid.sweetness.com”. They would then bond this collection study to my developer statement so nobody added could upload an app with that collection name… so my unpublished beta with collection study “meaningoflife.phandroid.sweetness.com” would be junked to whatever anticipative thief.
Hey Developers, Protect Yourself!
If you’ve already paying for a developer account, it costs you null to publicize an app or game. Why not denomination your app “Private Beta: App Name”, opt a clannish beta collection name, countersign protect your app so exclusive those who you provide the countersign to crapper effort it out, publicize to Android Market, and attain trusty every APK you deal has that aforementioned collection name?
Problem solved. Developers CAN protect themselves… but it wouldn’t perceive if Google locate whatever measures into locate to preclude the intense guys from doing insane things. Afterall, whatever grouping don’t poverty their apps or games to materialize on mart at ALL preceding to launch.
So, developers… hit daylong nights and cheetoh-stained fingers led you to whatever another revelations on how you, and man developers, crapper protect their hornlike work?




Let’s move discover with the Samsung 4G LTE which has a 4.3-inch screen, 8MP side camera, 1.3 front-facing camera, 4G capabilty of course, runs on Android 2.2. Full follows:
Then we’ve got the already well-known Tab, but the agreeably coercive 4G edition ():
And terminal but not least, the non-Android but staleness allow because I couldn’t yield it discover because I’m not a meanie, the Samsung 4G LTE Hotspot ().







