Android app publishing and distributing

Publishing to Google Play is the process that allows you to deliver your app to all users with a suitable Android device – or at least for a group of users you’ve selected. That’s why it is necessary to take this very seriously and to make sure all the final preparations and polishing is done well.

Make sure you publish your app after full development and testing cycles, when the debug phase is done. For successful publishing to Google Play, please make sure your app satisfies Google requirements, including functionality, user interface, Android material design requirements and other specifications.

What should be checked before publishing

  • Make sure your application is configured for the release, not debug;
  • Use proguard obfuscation to decrease the build size and optimize your code.
  • Use release build type if your IDE is gradle;
  • Sign the release version of your app – otherwise it will not be accepted;
  • Make sure that your app replies to all latest Android material design requirements;
  • Test your release app version on the target devices. If you lack testers or devices, just leave us a note and our crowd testers will test your app on the top devices you’ve selected;
  • Make sure your app resources are located on proper production servers or included into your app;
  • Create the final icon for your app.
  • Once the app is prepared for release and signed, you can publish it for app distribution among a wide group of users.

    How to select the method of your mobile app distribution

    There are different ways you can publish your app and make it available for users. Of course, the preferable one is to place your app at Google Play, the official marketplace for Android applications. But if you would like your app to pass regression testing by Ubertesters crowd community or to be distributed to a limited group of users or beta-testers, you need to select from the alternative ways.

    Usually, the alternative distribution methods include:

  • Sending the app via email;
  • Installing the app directly by connecting the device to a computer;
  • Over-the-air distribution.
  • App distribution via email

    If you do not know, how to distribute your mobile app, distribution via email is the easiest way. You just need to attach the necessary app version to the email and send it to the trusted users. However, this method hides a lot of disadvantages, where the main one is a security breach and the possibility of unauthorized mobile app distribution by other users.

    Direct installation via cable

    This is a secure method, but it requires the presence of a user with a device next to the developer. It makes direct distribution an inconvenient way, possible for very limited groups of internal testers.

    Over-the-air app distribution

    Over-the-air distribution is the most convenient way to distribute your app before its final publishing to Google Play. Usually over-the-air is provided by the external mobile testing platform that gives the possibility to install the app through its website or mobile service. Before using such a service, please make sure it provides controlled OTA – the ability to provide and restrict an access to the users when you need to.

    Our Ubertesters platform allows users to fully control over-the-air distribution, including build and user management, so your app is securely protected from unauthorized access and pirates. You can manage an access to particular users or user groups and deliver your app to all your beta-users or testers within a few minutes.

    If you are using OTA, please do not forget to enable the option ‘Unknown sources’ in your device’s settings – otherwise, Android system will not allow you to install the app from non-market place resource.

    Comments
    Harvey Specter
    Posted at 7:33 am June 9, 2016
    Edward
    Reply
    Author

    Thank you for sharing tips before publishing and distributing Android mobile app. Very informative insight!

      Harvey Specter
      Posted at 12:34 pm June 13, 2016
      Ran Rachlin
      Reply
      Author

      Thank you for your comment, Edward.

    Leave a Reply

    You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>