6. Get Your Crash Reporting Tool Ready

If you haven’t integrated a crash reporting tool in your app before releasing it yet, do it now.

The last thing you want, is to release your app into the wild and and not know anything about what’s happening with it. If your app crashes, you as the developer should have every possible information about it so that you can take the necessary steps to fix it immediately.

I would personally recommend using Crashlytics or Instabug at this point of time. I have been using it for more than an year now and am completely satisfied with it.

Also remember to log the caught exceptions explicitly. A caught exception is still an exception and you need to know everywhere its happening in your app, so that you can find better ways to improve your app.

There are some crashes or exceptions which only occur on a particular device or a particular Android version and you need to specifically deal with them.

A good crash reporting tool is like a good friend who will constantly help you and guide you to get better with time.

Recommended Reading

7. Test Your App On Different Devices

You probably have been using one or two devices to develop your app and have thoroughly tested on them. You have squashed all bugs and crashes and is ready to release, but wait! It’s just the tip of the iceberg.

You need to test your app thoroughly on various Android platforms and also on various device models from at least some popular manufacturers like Samsung, LG, HTC, Motorola who hold a considerable amount of market share in Android.

There are several minor to major API changes in every version of Android which needs to be dealt specifically. If you are doing heavy file-handling, then you must test properly on various platform versions (remember what Google did with KitKat) and also on devices from various manufacturers.

Almost all OEMs customize their ROMs in an attempt to create an unique experience for their users which makes it even more important to test your app on them before making a final releasing.

Buying a lot of devices for an individual developer can be a real pain. I wish I had an arsenal of devices to test on, but Santa keeps on ignoring my letters everytime.

Bonus: Testing on emulators like Genymotion can help you cover the basic tests to some extent, but there is nothing that can replace a real device.

8. Plug In Your Favourite Analytics Tool

With your app released in the market, you would want to know how your users are using the app, which features of your app are the most used and which are the ones completely ignored (and how you can improve them).

You need to know which screens users are spending most of their time on and where they are absolutely not. Armed with these valuable pieces of informations, you can decide where to spend your time, effort and money on. You can effectively decide the future game plan of your app.

There are several analytics tools out there, both paid and free. But the free ones are more than enough for small, mid-scale and even some large-scale apps.

You can try Firebase Analytics. It’s completely free with unlimited event tracking, really cool isn’t it? I have also used and have been a big fan of the realtime analytics offered by Answers from Fabric.

9. Make A Proper Release Plan

You have worked so hard on your app for months and you don’t want to screw your app release out of hurry, right?

Don’t just go ahead and put your app on the Play Store immediately. Spend some time in making a proper release plan. First make a small Alpha release of your app to some of your offline friends.

You can directly observe how these users are using your app, where are they getting stuck, what initial impressions are they having. Make a proper mix of both techie and non-techie users to have much better results.

After a few small alpha releases and initial improvements, you can go ahead with a Beta release. This can and should be big.

You can try out the open beta release system recently started by Google Play. With a Beta release, you will have a much bigger and better insight of the state of your product.

Various users from various countries having various devices will be using your app and this is EXACTLY what you want. Get ready to witness a lot of bugs and crashes. But in the end you will get some invaluable feedbacks which will help you to significantly improve your app.

Now your app is ready for a final release. You can be quite assured that no major issue can come up now. You can even refine the experience of your final release, by opting for a staged rollout where you push the final version of your app incrementally to small portions of your users.

Pro Tip: You can also try Beta by CrashAnalytics to seamlessly manage and distribute your beta app.

10. Haven’t Decided Your App’s Min SDK Yet?

It’s the right time to finalize the minimum SDK you are going to support. It basically depends on the features your app wants to support and the user base it wants to target. There should be a proper balance between these two.

If your app is using several non-backportable Material Design APIs, then you have to keep your min SDK to 21 (Lollipop). You wouldn’t probably want this as only 40% of the current user base is using Lollipop and above. You don’t want to miss out on such a huge volume of potential users, right?

Spend time on backporting features if you haven’t done it yet. If you decide to support API level 19 (Kitkat) and above, your potential user base jumps significantly from 40% to around 75%.

But my personal advice would be to support API level 15 and above (if possible) which lets you tap into above 97% of the current Android user base.

11. Make Way for Easy User Feedbacks

Once your app is released and your users start using it, they will face some issues or have some suggestions and would like to get in touch with you directly.

It is very important to implement a proper feedback mechanism in your app.

Try to place the feedback action somewhere in the Navigation Drawer or in the Toolbar, so that it is easily accessible to your users.

Also consider adding some FAQs in the feedback section which can solve some of the common queries almost immediately. This will not only save your users some valuable time, but will also save you from attending lesser support mails.

You should also give access to a public issue tracker (in Github maybe) so that your users can list down the bugs that they discover and it is also visible to all other users of your app.

It is very important to be transparent to your users.

Bonus: If you want an enterprise level feedback solution and can afford it, you should try UserVoice or ZenDesk.

12. Start Investing Your Time on ASO

Haven’t heard of the term App Store Optimization (ASO) yet? It’s the right time to start learning about it. ASO is all about how you can optimize your app and your app’s listing on Play Store to attract organic downloads from the store.

Start preparing some clean and beautiful promotional graphics for your Play Store page. It is even better if you can record a small video showing off some of the coolest features of the app.

I have seen many developers making the mistake of writing their Play Store page description just before releasing their app. Don’t do it. Spend a considerable amount of time and effort researching how you can write an optimized description which can drive organic downloads. But don’t overdo it or make it look spammy.

Spend time researching on the keywords you are going to target and how you are going to incorporate them in your page’s title and description. Thoroughly research who your competitors are and what they are doing to improve their rankings?

Rome was not built in a day.

You can not get your app optimized and ranked well within days. It takes time and money, but once you get it right, you are on the path to reach your next few million users.

Bonus: Use services like SensorTower or AppAnnie to get a complete insight into your competition and how you can improve your Play Store ranking.

13. Decide a Proper Release Date

This is important. Plan a proper release date so that you or your team is available for the next few days after the app is released.

I had a bitter experience of making a big mistake when I had released a major bug fix update on a Friday and went on to a vacation for the weekends. When I came back on Monday, I was greeted with lots of 1 star ratings and emails regarding a crash that all users of a particular Android version were seeing.

The issue was minor, but the impact was major. And it did hurt a lot.

This is something that you should religiously follow not only for your first release, but for every major update of your app. Always be prepared for contingency.

14. Give It The Last Finishing Touch

If you are taking care of all the points mentioned above, you are mostly good to go. But still there are some minor things that you may be interested implementing, to give your app the last finishing touch.

Before making the final release of your app, ensure all the TODOs have been addressed. We developers have a habit of adding TODOs whenever there is something we need to look into later, or whenever we get a bit lazy.

It’s also the right time to find a way to monetize your app. If you are good at something never do it for free. Either add in-app purchases or incorporate some ads (native ads, interstitial ads, etc) to start making money out of your product right away.

It is also a very good practice to add a change log so that your users know exactly what have been fixed or improved from the previous version. It is also a good practice to credit and add the license information of all the open-source libraries you are using.