How Often Should You Update Android Studio?
By Reto Meier, Google Android Promotion Engineer. Kay, Korea.
Android Tool Time Advanced Tips
Android Tool Time is a series of videos about Android tools.
One of Android Studio’s strengths is its rapid iteration and constant improvement. Each new release brings with it a slew of new features, new tools, and bug fixes, all of which can potentially increase your productivity.
You want to try all these new things, but you don’t want to risk leaving your current stable development environment. Which update channel do you use and how often do you receive updates?
Canary, Beta or Stable?
The Canary build is an early preview of what comes next. It includes exciting new features, but it’s not quite there yet, so it’s not very stable. Canary Channel always gets the latest build, even if it’s a new Beta or Stable release.
Beta is a backup to the stable version. It’s relatively buggy and stable. During the Canary iteration, the beta remained stationary, then updated weekly or biweekly until the stable release.
Stable is well tested and is considered more robust than the last Stable release. The frequency may vary, but it usually takes 6-10 weeks to update.
Use the Canary build for fun and usefulness
Using Canary is a double-edged sword:
- New features are available (such as Instant Run in Android 2.0) that can significantly improve your workflow.
- New features may not be reliable or easy to use, resulting in reduced productivity.
- Annoying and disruptive bugs almost always exist!
- Canary builds are unstable and prone to crashes.
I love messing with pre-released software. It’s fun to sneak in ahead of everyone else, and providing feedback on early products is the best way to have an impact.
But as an expert, putting me (or my team) at risk gave me pause.
When it came time to use the next Android OS dog food edition, I knew IT was time to take two phones with me.
So how do I use Android Studio?
Simultaneous installation, double fun
Install two versions of Android Studio at the same time, one stable and the other Canary, and you get the best of both worlds.
Check out the video here and below for details on installing multiple versions at once.
Install Both Canary and Stable Android Studio
Android Studio Settings are stored in version-specific directories; The exact location depends on the system used. So the two versions don’t interfere with each other.
You can use the new features, see which bugs have been fixed, and see if any issues affecting your workflow have been fixed in the next stable release.
If you find canary is becoming more stable and less disruptive, you’ll be more confident that you can accept it when the next stable version is released.
About Update Frequency
You probably downloaded the first Canary build when it was released, played with it for a while, ran into bugs, and then went back to your stable environment.
The first version of Canary was the smallest visible product, and each subsequent build brings significant improvements over the previous version; So it’s worth getting every update as soon as possible.
In this way, you should already be familiar with the build by the time the stable version is available. You’ll embrace it when the stable version comes out.
To get Updates notifications, open the Android Studio options menu, navigate to “System Settings” > “Updates” and make sure “Automatically Check Updates” is checked.
How is dual installation used in practice?
It depends on your tolerance for distractions. I personally use Canary like this:
Check whether the image uses the “decision Algorithm” of the current Canary
For me personally, I do it every day. Another approach is to do this every time a new Canary is released.
What bugs will block you depends on your workflow and how many curses you can tolerate per minute (the value of the ALLOWABLE_SWEARS_PER_MINUTE variable).
In either case, if you encounter a bug, please report it directly to the Android Studio team using the “Help” > “Submit Feedback” menu item. They sort through these bugs on a daily basis and use them to help determine when a Canary build can become a beta, and a beta can become a stable.
What are your tolerable curses per minute?
Trying new versions of Canary regularly will help you know what to expect, and you’ll have confidence in the reliability of each stable release as it’s perfected. Let you fully apply these improvements to your workflow.
You’ll also help the Android Studio team release new releases faster and make it more stable.
What’s your way of testing Android Studio Canary?
For more Android Studio tips, tricks, and release details, see the Android Tool Time video series on YouTube or Youku.
Review images
Unless otherwise stated, the content of this article is licensed under the Creative Commons Attribution 3.0 license, and the code samples are licensed under Apache 2.0. Please check our terms of Service for more details.