A new modern look for the Android brand
blog.google
blog.google
Or, shorter, making it too open and not distinguishing between the platform and vendor-specific implementations of it is allowing others to dilute the meaning of "Android" in a way that is detrimental to the brand.
It looks very amateur-ish to me, like someone's first Blender project.
https://commons.wikimedia.org/wiki/File:Android_robot_(2014-...
The camera still crashes if you take too many photos too quickly... The backup service still does a shitty job and doesn't backup some apps... The phone still occasionally randomly gets hot and drains the battery by midday... Sharing a file with another android user over bluetooth/wifi/nearby share still fails more often than not. A VoIP/video call still stutters and glitches when you switch from wifi to cell or vice versa.
The fact I can list 5 bugs from memory that have existed for 10 years is a sign that perhaps those 10,000 minds may be misplaced.
I'd be curious if you or anyone else has any ideas on preventing that, because I think it's impossible? A voip or video call uses one or more network sockets. If I'm using wifi, that socket goes over my network, which the server communicates with. If I suddenly switch to cellular, there will always need to be a reconnection over the cellular network, because the server was previously communicating over a completely different network route.
It could have a transition period where the data is sent over both networks for a few seconds until the transfer could be completed seamlessly.
Sure, it would require app support, and server support, but if the OS supported it I'm pretty sure app and server support would happen.
Alas - sadly it's currently impossible for an app to talk over both wifi and cellular at the same time on android - although it is possible for two different apps to each be talking over different networks at the same time. This functionality is used for the captive portal signin screen so you can be signing in to one network while still connected to another.
Tested this on: Nexus 4, Nexus 5, Nexus 6P, Pixel 1, Pixel 5, Pixel 7.
Full res video: https://storage.googleapis.com/gweb-uniblog-publish-prod/ori...
The full res clearly has an existing vid imported in where the color space was incorrect. The bottom right droid looks like it was exported as a gif in a reduced color space. This is extremely sloppy for a rebrand announcement.
Edit: It gets even better, the bottom gif doesn't loop for the entire duration of the video. It stops 13s into the 16s video.
The rest is bad enough, but I could not believe that until I saw it for myself. It is honestly like some highschool level presentation video or something.
One thing that bugs me a bit too, is when the left hand bugdroid jumps up, the legs have some kind of glossy shine, when then just pops away. Not sure if that intentional, but it is very jarring to me.
Interestingly I can't seem to find anyone else complaining that Chrome on wayland only does nearest-neighbour resizes of videos. I wonder if it's crappiness in the hardware video decoder or a deliberate performance decision because my hardware is slow at texture resizing?
Oh, and what appears to be a failure to comply with cookie laws (UK).