How to upload an app to the Google Play store?

-

     You wrote an amazing app, it works on various resolutions and many tested and trusted devices, so the next step is to upload it to the Google Play store ! but wait, what's the best way to do it?

This link explains all the important things you should do in order to prepare your app for publishing

we'll cover the more important stuff.

follow these next steps and you'll be on the market in no time:

1. Go over the code and remove all unnecessary code (Logs..unused code, unused

    resources..etc..)

2. Choose a good package name - this will be your identifier for the store (on upgrade/update

    we must use the same package name)

3. remove the android:debuggable attribute from your manifest file if exists

4. Don't forget an icon for the app

5. If you're supporting different resolutions - include matching graphics resources for them

6. We'll be using Eclipse's export wizard in order to get our app to "release" mode

    To create a signed and aligned APK in Eclipse:

  • Select the project in the Package Explorer and select File > Export.
  • Open the Android folder, select Export Android Application, and click Next.
  • Complete the Export Wizard and your application will be compiled, signed, aligned, and ready for distribution.

The Export Android Application wizard now starts, which will guide you through the  process of signing your application, including steps for selecting the private key with which to sign the APK (or creating a new keystore and private key) - I recommend creating a  new keystore and save it somewhere good.

7. Now you have a release ready APK file, the next step is to sign up to a developer account at

Google Play store (it costs 25$ for registration - for as many apps you like)

8. follow the wizard on the Google Play Store dashboard - it's quite simple from here

Congrats !

your first app is on the Play Store !

Comments

Post a Comment

Popular posts from this blog

Spinner VS AutoCompleteTextView

-
Image
       We’ve all been in a situation where we needed to show a list of some sort, a list which should be triggered by a user interaction (click, tap, etc..) A list is simple enough, probably even a spinner if we don’t want to spend that much screen real-estate on showing a list which the user clicks once and probably doesn’t need to see it after that. A spinner can be a real bug once there are too much entries for the user to choose from, how much is too much? that’s a good question – probably it differs from user to user, and probably this will have some performance issues with areal large number of entries, you cannot scroll forever to find what you’re looking for. A simple solutions for the problems mentioned above is an AutoCompleteTextView. it’s a control which is basically a combination of a TextView, EditText, and a Spinner all wrapped up in a single easy to use and configurable control. let’s see how it’s done:   first, in the layout file, c...
Read more

Utilizing Http response cache

-
     A typical mobile application will probably consume some resources from a web server using http requests. This repeated task has some drawbacks: Bandwidth has a cost, polling the same data over and over again results in a waste of user’s quota. the responsiveness and user experience is compromised once the user keeps waiting for data. If the requested data hasn’t changed on the server, then there’s no reason for us to fetch it. Of course, local caching of data is a must, but we also need to be able to refresh the data if it has changed on the server. A simple solution which comes out of the box for API 4+ is http response caching. Http response caching is a mechanism which enables us as developers to save a footprint of the response utilizing the abilities of the Http protocol. Basically, is holds a simple cache of the response which can be defined and enabled in code, and it prevents from fetching unchanged data from the server which was already fetched a...
Read more

ORM for android

-
     ORM – Object relational mapping has been around for quite some time now. Basically it’s a piece of software (regardless of targeted platform), which simplifies the connection between objects (as in OOP) and data in database (mostly used is tables based relational database), and it exists in order to help simplify bridging the gap between the two in our development process.     Microsoft's Entity framework is a great example for a robust easy to use framework which allows creating and querying the database from an object’s point of view with classic object oriented programming paradigms while maintaining all DB construction’s needs such as relationships between objects (tables) such as one to many or many to many including all the indexing, optimization etc..      In android, we have SQLite as a database platform, from simple to advanced application, it’s likely to assume that we’ll need some relational database to store and r...
Read more