At the very end of last week I finished an update to Betan that will enable other developers to distribute their applications using the same tools I use to share private copies (usually betas) with users. My website provides details about Betan
I don’t know whether other developers will be actually motivated to use Betan, since it does involve at least one additional step over simpler mechanism such as just emailing the APK. The developer needs to encrypt the published APKs.
What motivated me to produce a more secure way of distributing beta copies of my applications was not that, if the APK was shared, some people would be able to use my application illegitimately. Instead I’m more motivated by ensuring that my users have a well tested product, however they procured the application — this is my reason for sharing beta copies in the first place.
The possibility that some poorly tested APK which erroneously wipes user data might gain broad distribution is enough of a motivation for me to write Betan. It may not be enough of a reason for other developers, in which case I may remain the only listed Pubisher.
This would be a shame, but the work to broaden access to Betan was not that great thanks to the rapidity with which I was able to put a simple web app together using GAE and GWT (about 4 hours). Most of the work consisted of tightening-up the command-line tool, tweaks to the android application (mostly listing publishers and better landscape support) and documentation.
Whether or not Betan is adopted by other developers, at least one more revision is planned — it will finish support for constraints on the phones to which applications can be installed and provide automatic notifications to users when newer versions become available.
