3. Android App signing and publishing

First, ask a question, why do we need signature and version control?

The program is done, we have to put it on the market for commercial release.

Second, the release process

"Ready to publish"

1) Remove log, set the version number and name.

2) sign through the ADT tool.

3) Finally release the test for your publishing terminal.

4) Update the release resources.

5) Prepare the remote server your application relies on.

"Publish to User"

Direct APK spread

On the website for download, OTA server

On the market for download

"Automatic Version upgrade feature"

Method One:

1, provide an HTTP APK address, and provide a WebService detect the latest version

2, when the application starts to call WebService, if the server has a newer version, pop up the upgrade prompt box, customers choose to upgrade, access to the APK URL.

(Open web Browser, Download, manually click on the downloaded file, (notification)

Method Two:

With a similar

Write your own program to download, Stream.

Install

Method Three:

Put it on the Android market.

market://....apk

Third, the procedure signature

Symmetric encryption

Asymmetric encryption: Public key, private key (signature and authentication).

Iv. version management of the program

3. Android App signing and publishing