Canary is the most unstable version of Chrome publicly available, created daily from the most stable of the Chrome team’s last 40 revisions. It is so fraught with data peril, in fact, that it runs alongside other Chrome releases, does not share files with any other Chrome installation, silos profile, settings, plugin, and theme data. By default, in fact, Chrome Canary cannot be set as the default browser on Windows or Mac — that preference has to be changed at the operating system level.
Chrome Canary for Android seems no different. The Play Store listing describes it as “experimental,” and a release that “has not been tested,” and one that “may be unstable” at times.” Just like the Canary channel for other platforms, new versions are built from the most recent code available and often contain a variety of new features, enhancements, and bug fixes,” Google said in a blog post. “These builds shipped automatically with now manual testing, which means that the build can be unstable and may even stop working entirely for days at a time.”
Google also warns Canary will see frequent updates — up to “seven times per week” — and so potentially consume more bandwidth than other, slightly more polished browsers. “The frequency of builds means that keeping the app update will consume … typically more than 100MB,” Google said. “This is especially important for phones set to update native apps over cellular data.”
All that said, Canary is hardly a lost cause. “The goal is for Canary to remain usable at all times,” Google said. The takeaway: as long as you don’t mind a bit of unpredictability, Canary will not give you any major trouble. Just don’t trust it with your manifesto. “The Chrome team prioritizes fixing major issues as quickly as possible,” Google said.
Chrome Canary joins the two other prerelease Chrome versions on Android, Chrome Beta and Chrome Dev. The former became available in January 2013 and the latter launched in April 2015.
