I'm surprised they didn't have live notifications or desktop windowing. I guess features like that go from Android OEMs, to iOS, then to Android itself. Do Google have their own Pixel versions of things like that before they make it to Android though?
Android 16 is here
111–120 of 360 posts
Re: Android 16 is here
#112I like their Material Expressive design a lot more now after Apple's big reveal. While it's still a bit too colorful and whimsical for my liking, it does stay much closer to what I think should be the top UX design ideal - be clear, legible, and get out of the way . On the new iOS every screen feels like some UX designer is shouting "look how amazing I am at this!!" at me.
My main complaint with Material Expressive is that every other button seems to be 85% padding and 15% actual content. What happened to reasonable information density?
Re: Android 16 is here
#113Earlier quoted context omitted.
For control surfaces, padding prevents misclicks. It's actually very important part of perceived interface quality when dealing with a handheld touchscreen device.
Different topic: CSS doesn't have a good way to manage nearby clicks? A tap just a few px outside a button should click the button? s can steal focus from nearby taps on Mobile Safari (which can also be a fuckup). I hate iPhone taps that slip a little and scrollable areas having queer interactions (causing usability/accessibility issues).
It's just as bad to click a button you don't want to, when you're merely trying to scroll, or highlight text, or click another button.
Making a button's clickable area larger than the button itself can be desirable in limited circumstances, but it's not a general-purpose solution.
Re: Android 16 is here
#114Earlier quoted context omitted.
UI engineers should be like vaccines. If they do their job well, you should never see why they were needed.
That so many do not see why vaccines are needed is a serious problem.
We shouldn't do that, in the same way we shouldn't make sure people know UI is important by changing it completely every n years.
Re: Android 16 is here
#115Earlier quoted context omitted.
This knee-jerk reaction is correct more often than not (see the terrible iOS redesign announced earlier), but in this case it seems like it might be incorrect? I looked through the highlights linked here and the full "What's New" page [0] and am pleasantly surprised to see a few new features but no major overhauls of existing ones. [0] https://www.android.com/16
The issue is this reaction never sticks. Everyone's up in arms, but would you really want to go back to Android KitKat or iOS 2? Probably not for more than novelty, right?
I like a lot of the new features, but the visual (mis)communication language is terrible.
Re: Android 16 is here
#116Re: Android 16 is here
#117Earlier quoted context omitted.
I wish we had a dozen phone companies instead of just two. Please write your legislators and demand antitrust action against Apple and Google for the following: - Lack of One-Tap Web Installs (without scare walls or buried settings menus). This is the biggest stranglehold they have. Web installs can be done safely and securely via app signing, permissions, and signature blacklists. - First-party defaults for all the…
> - First-party defaults for all the platform pieces: Messaging, Payments, Photos, Music, Media, Navigation, etc. Every single one of these lets Apple and Google squeeze another industry and forces us into a pit of no-innovation. Don't/can't Android manufacturers provide alternative defaults here?
Manufacturers were contractually forbidden from doing that.
Re: Android 16 is here
#118Oh great, I get to learn how to use my phone all over again. We need a "leave this the $EXPLETIVE alone" setting for our user interfaces.
I wish we had a dozen phone companies instead of just two. Please write your legislators and demand antitrust action against Apple and Google for the following: - Lack of One-Tap Web Installs (without scare walls or buried settings menus). This is the biggest stranglehold they have. Web installs can be done safely and securely via app signing, permissions, and signature blacklists. - First-party defaults for all the…
Counterpoint: the resources currently dedicated to Apple and Android would then be spread across a dozen operating systems, assuming constant consumer spending.
Maybe you think stasis is a good thing, but I (mostly) appreciate the progress iOS and Android have made over the past nearly two decades. I wouldn't want to currently be stuck at iOS 3 or 4 as opposed to iOS 18.
Assuming you actually mean a dozen phone operating systems. Because we already do have lots of phone companies, but they mostly all use Android.
Re: Android 16 is here
#119Are they still moving forward with killing AOSP?
Re: Android 16 is here
#120Earlier quoted context omitted.
This knee-jerk reaction is correct more often than not (see the terrible iOS redesign announced earlier), but in this case it seems like it might be incorrect? I looked through the highlights linked here and the full "What's New" page [0] and am pleasantly surprised to see a few new features but no major overhauls of existing ones. [0] https://www.android.com/16
The issue is this reaction never sticks. Everyone's up in arms, but would you really want to go back to Android KitKat or iOS 2? Probably not for more than novelty, right?