Android Simple Development Tutorial 23: Publishing Applications

Here is a basic introduction of Android development of some of the basic knowledge, in the development of practical applications, the most commonly used references are:

The Developer ' s Guide

Android References

Android Resources

The last one is google.com:-).

After the application is written, after testing on the device, the final step is to publish your application. Like the Java ME platform, Android apps need to be digitally signed before they can be published. Unlike the Java me, however, the digital certificate that Android uses to sign does not require CA authentication, which saves $400-$500 every year, and the IPhone costs $ $ a year. Android platform Development is the least investment for developers and one of the most promising mobile platforms in the long run.

Before publishing Android apps, you can use tools such as keytool） creating a private key to digitally sign an application. Keytool is in the JDK.

Usage is as follows:

$ keytool-genkey-v-keystore My-release-key.keystore
-alias Alias_name-keyalg rsa-keysize 2048-validity 10000

The specific meaning can see: http://developer.android.com/guide/publishing/app-signing.html

In addition to digital signatures, the application can also be scrambling, if the use of Eclipse to develop Android applications, in the creation of each Android application has a proguard.cfg file, generally use the default settings. The advantage of scrambling code (or confusion) is to protect the source code and remove some unwanted codes that can be the last release package greatly reduced. Detailed usage of Proguard can be found in http://proguard.sourceforge.net/

If you use Eclipse to publish your final. apk file, you can do it step-by-step through the Android Tool Menu Wizard:

See a full set of tutorials: http://www.bianceng.cn/OS/extra/201301/35252.htm