The number one issue I have with Android is that while this looks cool, because of the fragmentation of the OS delivery between vendors- I have no idea which phone or timeframe when I could see the rollout of Material 3 Expressive.<p>More than 10 years later, shopping for an Android phone with the latest OS is a nightmare. Android leadership keeps on getting shuffled around, Google changes priorities every 6 months it seems. Despite Apple flubbing the ball on AI, at least I know that the phone will be supported for at least 4 years.<p>They will need to improve on their ecosystem commitments if they'd like people like me to switch back.
I wish Google would stick with a design paradigm for a bit for once.<p>It's not just their own apps that need updating, it's everyone else's, too. Most of which will never happen, so users are stuck in a hodgepodge of several generations of different design paradigms.<p>Material was fine. So was Material 2. So was Material 3. So is Material 3 Expressive, I guess. Just stick with something!
> You can now customize Quick Settings to squeeze in more of your favorite actions like Flashlight and Do Not Disturb.<p>I feel I'm missing something. Hasn't customizing the quick settings been possible forever?<p>In fact the only thing preventing me from having the single tap Do Not Disturb in the quick settings <i>is that these same UX people removed the option in the latest version of Android</i>, and buried it in a "Modes" menu for no reason at all.<p>Super happy to have that back, but good grief, trying to pitch a rollback as an innovative new feature is pretty audacious.
An article that's not even 600 words long immediately offering to use AI to make itself even shorter has to be up there on the useless-AI-shit-for-the-sake-of-it leaderboard.
Given how much of a downgrade the last visual refresh was (Android 12 I think?), this is news I do not welcome. Anyone else remember the lock screen being a giant two line clock with no way to customize it, or the way the settings buttons got way bigger for no good reason? It was awful. I don't look forward to seeing what they will screw up this time.
Android Kiki to Android Bouba evolution:<p>From square icons and sharp Roboto to blobby amoeba-shaped designs and rounded fonts.<p>Also, Chile mentioned!
Am I the only one who -hates- these springy animations? I feel it introduces an artificial lag. When I tap I want instant response, I don't want to have to wait a half second for the boxes to complete their scale transforms.<p>My canonical example is deleting message threads out of iOS Messages app. For every row in the list you need to swipe allll the way over to the left, wait for the stupid animation, click delete, wait for the stupid animation, click the confirm. Maybe it would improve if the component was responsive during its animation cycle. But ugh.
"Big refresh" seems like an exaggeration compared to the overhauls Android has gotten in the past. These are pretty subtle design tweaks. Which is fine; I don't think Android particularly needs a huge overhaul at this point.
Looks seriously ugly but beauty is in the eye of the beholder and that's only my personal opinion.
Thankfully I won't ever get to see it anyway as majority Android vendors aren't using any of Google's UI stuff (my Oppo Find N5 basically looks iPhoney with ColorOS).
So really this should be titled "Google Pixel phones will be getting..."
Differently-shaped buttons and more swoopy animations are not what Wear OS needs. Wear OS needs better information density and more attention to detail in interaction design and implementation rather than appearance. The whole thing feels like it was designed in After Effects and implemented to spec with no user feedback in the process at all.<p>I continue to strongly prefer the Pebble UI after all these years. It just does a much better job with the basics like notifications and alarms. it's not even close.
I actually thinks this looks great as a current iOS user. Apple's latest software quality (or lack of it) has made me want to try out Android again.
I would like to hear how that fluid UI works on that circular display, that looks like an absolute pain to get right. I think I could boil my brain just thinking about how they might have begun to tackle that and all the challenges they had. Just dealing with Unicode and nothing else for dynamically resizing shapes is a headache in the making.
Good lord I do not need my phone to be "expressive". I need the camera to open without janking out my podcasts, I need my browser to not have to reload pages if I switch to another app, I need my password manager to be able to reliably autofill apps. I do not need "expressive".
Google is allergic to normal interfaces nowadays. Everything about Material when it rolled out rubbed me the wrong way, Rounded edges? Extra real estate? Everything is bubbles.<p>I'll take cold, basic, and data-full interfaces instead of the wasted real estate in the era of CSS-ifying every user interaction to death.
Another "big refresh". I've already disabled animations because of the faintly ridiculous system-wide overscroll effect [0] which makes every menu and webpage bounce like the viewport is made of gelatin, so I'm a little bemused to see them doubling down on "natural, springy animations". I know this is "old man yelling at cloud" of me, but I don't care for my notifications to "subtly respond" to adjacent ones being dragged.<p>[0] <a href="https://github.com/flutter/flutter/issues/83355">https://github.com/flutter/flutter/issues/83355</a>
This will be my last Pixel phone. I had the original and it was perfect. No fluff. Simple. Each version gets worse and worse. 7 is horrible. Still can't remove the stupid date from the home screen.
So many people I work with (in tech) were on Android for years, and all eventually switched to iOS.<p>My biggest issue with Google is they aren't convicted in anything they do. They just guess, or try 5 different things, and see what sticks. That makes it a mess for users, as the UX constantly changes.<p>I also can't understand why Google decided a circular face made sense for Wear. It's good for analogue watches, and garbage for everything else. Try reading a message where words are either cut off, or you're stuck basically using a square inside the circle. It makes no sense other than because Google didn't want to 'copy' Apple with the rectangular shape.
The Wear OS looks the most exciting here. I'm looking forward to a Pixel 4 Watch with a better battery life, having google maps and android app support.
> Man, I wish my Android had 'better' UI<p>Is what I have never, ever heard. I don't what to shit on designers, who also need to justify their job, but it would be cool to see some ACTUAL improvements to important things. Like battery life.
Wear OS needs core development and an army of QA testers, not another redesign. The design is fine, but overall the functionality of the product feels like a beta test (and I think that's being generous), even on their own hardware.<p>I answer a call on my phone and the audio is routed to my watch, or vice versa, the official weather app claims it can't get my location even though it has access to the GPS (and it's actively being used by Fitbit to track exercise) and wifi positioning. Google Maps on the watch doesn't load results half the time, the other half the time it'll get stuck on "starting navigation" - sometimes unstuck by launching Maps on the phone (despite having offline maps downloaded to the watch) and other times it's just stuck forever. Fitbit will display some static/mock/fake exercise values until the display is woken up when OS-level always on display is disabled but AOD is enabled in Fitbit during exercise. I could go on.
We keep making the screens bigger to make the interfaces even more dumbed down and stupid.<p>Are we in Idiocracy at this point or what, Google?<p>Some of you fuckers need to go pick back up The Zen of Palm and re-read it because y'all have no idea what you're shipping these days in comparison.<p><a href="https://archive.org/details/zen-of-palm" rel="nofollow">https://archive.org/details/zen-of-palm</a>
This is just shit, a horrible redesign. I'd much rather "truly express" myself by keeping high information density in the user interface instead of picking color palettes for this trendy "bouba" bullshit. It's as bad a redesign as the recent Bluetooth option, which went from a single click to turn it off (and respecting airplane mode) to multiple clicks and staying on between Android 14 and 15. Of course Google wants BT scanning to work even if you're in airplane mode, they didn't do it for my convenience. I've had enough and am not updating anymore, outside of security updates. Now I use Rethink as on-device VPN and every app, system or not, has no access to the network unless I explicitly enable it, no more nagging to update.
Wew, this is great and all, but when am I going to be able to disable the list of trending topics or search history in my search bar, or at least hide it entirely? Never? I have to learn about the spirit airlines emergency landing and some bs about the NFL even though I'm not even in that country? Idk that customization feels paramount if I can't control what I see as I'm using the device.
i like the changes are coming but i wish they didn't remove the old look<p>I mean... what if i prefer the older version of the UI? my only option is a different launcher or not updating
Looks like shit. It seems that on every UI/UX update, Google products become shittier.<p>I'll keep using Android anyway because I find Apple UI/UX even more disgusting.<p>Smartphones don't matter anyway. What most people do in high end devices can be done in mid-tier or even shit-tier devices too.
As an iOS user so many of the headline effects this Android update mentions seem to be already part of my iOS experience. Thus this seems to be catch ups to iOS.
In human–computer interaction, baby duck syndrome denotes the tendency for computer users to "imprint" on the first system they learn, then judge other systems by their similarity to that first system. The result is that "users generally prefer systems similar to those they learned on and dislike unfamiliar systems". The issue may present itself relatively early in a computer user's experience, and it has been observed to impede education of students in new software systems or user interfaces.<p><a href="https://en.m.wikipedia.org/wiki/Imprinting_(psychology)#Baby_duck_syndrome" rel="nofollow">https://en.m.wikipedia.org/wiki/Imprinting_(psychology)#Baby...</a>