Over a million developers have joined DZone.

Android Studio Tips: Publishing with Gradle

DZone's Guide to

Android Studio Tips: Publishing with Gradle

· Java Zone
Free Resource

The single app analytics solutions to take your web and mobile apps to the next level.  Try today!  Brought to you in partnership with CA Technologies

We've heard some tips on what you ought to know before switching from Eclipse to Android Studio, as well as some general thoughts on how great it is to do so, but one of the major and daunting differences between the two IDEs is the build tool: Android Studio uses Gradle instead of Ant. For those who aren't used to it, it can be a bit of a challenge to get used to, so Damian Mee has published a walkthrough of the Gradle build process in Android Studio, which covers all the more subtle tips and tricks one might need to know to succeed.

First, Mee covers some of the basics that need to be addressed in Android Studio itself. He breaks it down into three quick steps:

  • "Know what to click"
  • "Know 'the code'"
  • "Know where to look"

Then, Mee goes into detail on each of the Gradle flows he has used to publish his apps. These are more of an evolution than a list of options, but he still explains each, as they are all helpful in understanding the next stage in the progression. He calls the flows:

  • Convenient flow
  • Shared Repo flow
  • Awesome flow
  • Perfect flow

The last one being his current approach. As the introduction of Gradle is one of the biggest differences in Android Studio, this is a welcome resource and should solve a bit of confusion for newcomers. Check out the full article for more details.

CA App Experience Analytics, a whole new level of visibility. Learn more. Brought to you in partnership with CA Technologies.


Opinions expressed by DZone contributors are their own.


Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.


{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}