[ad_1]
I think it’s fair to say Android 12 hasn’t had the smoothest launch. Not only is it late (compared to the latest versions anyway), but now that it’s finally here, well, it’s not really.
Google has made the bizarre decision to launch Android 12 on the Android Open Source Project (AOSP), an open source version of the platform used by developers. That in itself isn’t strange – Google is always doing this with new releases, but it is also still releasing them on Pixel phones at the same time. Except this year.
This year, if you are a general user, there is no easy or official way to install Android 12 on your phone right now, even if you have a Google Pixel 5.
It’s a weird and confusing situation, with articles saying Android 12 is here when it’s functionally not, and with early reviews appearing that might not be everything. quite representative, because the version that even appears on Pixel phones is likely to be at least a little different.
This weird launch also means that when Android 12 finally hits phones, it will likely do so with less fanfare than normal, since it’s already released, sort of.
This appears to be a theme for Google in 2021, with the company also semi-announcing the Pixel 6 line in August, but leaving us to wait until October 19 for a full launch. But there at least it was creating a hype for phones, whereas with Android 12 it only creates confusion.
Why it happened and what should have happened
So why did Google do this? Essentially because the AOSP version of Android was finished, while the version that shipped to Pixel phones was not.
In a comment to Android Central, a Google spokesperson said, “We’re putting the finishing touches on a special release with Pixel-exclusive and Pixel-first experiences on Android 12. This will be rolled out to Pixel users across the board. next weeks.”
The team working on Android itself is also different from the team working on Pixel handsets. So while they probably communicate and coordinate a lot, the first team has finally finished their project, while the second has yet to add some finishing touches.
But just because one team finished before the other doesn’t mean they had to release Android 12 – in a form most people can’t use – before the Pixel version is finished. It looks like the wait is almost over for Android 12 on the Pixel, so couldn’t Google have waited a few more weeks and launched both versions together like any other year?
It would have avoided all of this confusion and criticism and allowed Android 12 to land with a bang rather than a whimper.
Why Google didn’t do this is not entirely clear. We can’t imagine this being due to a lack of communication between the two teams – although if it did, it’s a sign of much bigger and more systemic issues.
It’s more likely that the company simply decided that releasing Android on AOSP as soon as possible would be beneficial for developers. And Google is probably right, but if it was worth the confusion caused, we’re less sure.
It doesn’t help that some titles are adding to the confusion by saying Android 12 launched, without warning, but Google should have predicted that would happen.
An overwhelming contrast
Compare that to the launch of iOS 15 and it’s day and night. iOS 15 was announced on September 14 and went live less than a week later on September 20 – with that date confirmed on the day of the announcement.
It was also launched on that date for all compatible devices, going all the way back to the iPhone 6S from 2015. There has been no confusion, no uncertainty and no gradual roll-out.
Compare that to Android 12, which is here, except it’s not. It’s coming to Pixel phones soon, but we’re not sure when. When it lands on Pixel, we don’t even know for sure which models will be compatible. We’re expecting it from the Pixel 3, as it’s in beta, but Google hasn’t confirmed.
The Pixel 3 also released in 2018, so if that’s the limit, that means a lot less support than what Apple offers, although that’s nothing new for Android. Then, of course, it will be at least weeks and in many cases months before most handsets from other manufacturers get Android 12.
So there is an assortment of issues here, with many causes, and many of which are difficult to resolve. Some of these are issues that Android has always faced, but the last thing Google needs is to add to its problems. Android launches are always confusing, especially compared to iOS launches, but this year it’s downright confusing.
It’s such a shame, especially since Android 12 itself looks like an exciting update, with a complete visual overhaul. Google’s sloppy launch took away the shine somewhat, so hopefully the Android 13 launch gets more taken into account.
[ad_2]
Source link