The following is the first few sections of a chapter from The Busy Coder's Guide to Android Development, plus headings for the remaining major sections, to give you an idea about the content of the chapter.
Perhaps the most important step in preparing your application for production distribution is signing it with a production signing key. While mistakes here may not be immediately apparent, they can have significant long-term impacts, particularly when it comes time for you to distribute an update.
Understanding this chapter requires that you have read the core chapters of this book.
There are many reasons why Android wants you to sign your application with a production key. Here are perhaps the top three:
The latter one is the most important for you, if you plan on offering updates of your application. If you sign version 1.0 of your application with one key, and you sign version 2.0 of your application with another key, version 2.0 will not install over the top of version 1.0 — it will fail with a certificate-match error.
The preview of this section took that left turn at Albuquerque.
The preview of this section was traded for a bag of magic beans.