Live data from Hacker News

Android 16 is here

blog.google

311–320 of 360 posts

Re: Android 16 is here

#311

Earlier quoted context omitted.

Once unlocked, swipe down from the top of the screen to open Notification Center.

With a case on the phone, my success rate of swiping downwards like that is about 60%

Seems about right and the missing ones are the ones you're most likely to be the ones you don't understand.

The swiping downward is also fairly dumb. There zero discoverability and triggering it seems hit in miss.

If you have no notification swiping down also locks your phone, rather than telling you that you have zero notification... WHY?

Re: Android 16 is here

#312
Installed (Pixel Fold 1). Nothing is visibly different.

* Saw an unexpected notification post-upgrade that, when I clicked it, took me to the wrong place. It was about "Body Sensor" permission for "Fit" which I assumed meant Google Fit needed additional info about my private health info. A crappy workflow for me, since the warning was real, I became alarmed .. hoping that "Fit" really was simply Google Fit, and ended up in Google Play Services' app information settings sheet.

* Took me to a 'welcome to new pixel' which has overgrown its UX with OS 16. It had 3 'new' features to tell me about - something about 'VIP' which seemed like over-optimization of a workflow. Some other stuff which was not relevant to me (https://news.ycombinator.com/item?id=44245460). It also had an enormous list of differently colored (highlighted, not-highlighted) icons which led me to info about features, UGH .. in "Wizard" format (next, next, next) so I could not see an overview, nor know which I had previously viewed during the prior 15 OS iterations...so I abandoned that mini "Welcome" app.

-- Also, the mini videos in the "Welcome" app are inscrutable. My Pixel Fold 1 main screen is already small, and then the video illustrating the features is not zoomable. Clicking it merely pauses it. The videos show a hypothetical Pixel phone and a hypothetical human finger-tip dragging its way across the screen. Then the video wants me to read some of this 3x-too-small text, because THAT is the POINT of the video I had the most annoyance at .. the text content was somehow the feature. Yes I should have put my glasses on (+1.2 prescription - slight far-sighted), though it seems like I should be able to read the text-in-video from 2' away...it's literally the Welcome app, for ALL users, not some extra-niche app. Human Factors People gave zero shits about that IMO.

Re: Android 16 is here

#313
post #92

Earlier quoted context omitted.

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).

You could, but you don't want it to. Buttons are e.g. often floating above content, or adjacent to other buttons. 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.

As a proof.. well just use HN on your phone. It absolutely sucks, so those UI puritanists - please learn a lesson and at least make touch targets reasonably sized!

Re: Android 16 is here

#314
post #270

Earlier quoted context omitted.

>rooting should be allowed on a certified device I don't think this should be allowed because rooting breaks the Android security model. Devices that don't follow at least Android's security model should not be allowed that way apps understand the security model of Android. >grapheneos should be given a way to pass all attestations There already is the Android attestation API that can be used to attest grapheneos. Bu…

I think it's a bit disingenuous to mix together the security model and the ability to do things on a device you own. Should the default android be locked, with no root, play store verifying apps, etc, absolutely. This is great for the average user that desires nothing more than just running play store apps. Should you have the ability to run what you want on your phone, and copy the data from the app that you install…

>Should you have the ability to run what you want on your phone

Sure, but that doesn't require root to do. The OS can expose capabilities that apps want instead of requiring security to be entirely bypassed with root.

>and copy the data from the app that you installed, after accepting the risks?

No, because that violates Android's security model. If an app wants to have a authentication token live on a single device then being able to copy it violates that and can result in multiple different devices sharing the same token.

>Google/Main vendors is making it less and less possible

It's app developers doing this.

Re: Android 16 is here

#315

The more I compare Material 3 Expressive to Liquid Glass the more I'm excited to switch back to a Pixel. I'm a fan of the use of color, motions, and different shapes versus transparency, minimal contrast, and little color. I'm on a iPhone 13 Pro Max right now that's still doing well but starting to show battery capacity age. Plus, it's the only non-USB-C device I own so I'd be happy to get rid of it.

I'd move to a pixel if it was the same hardware value as the corresponding Samsung or OnePlus, they always just seem to be a year or two behind.

Re: Android 16 is here

#316
post #135
post #87

If Android is getting desktop windowing, how long until I can just plug my phone into a monitor and keyboard and have a usable computer?

You could do that for years with Samsung phones already.

You could do that for even more years with Motorola phones already.

Re: Android 16 is here

#317
post #270

Earlier quoted context omitted.

I think it's a bit disingenuous to mix together the security model and the ability to do things on a device you own. Should the default android be locked, with no root, play store verifying apps, etc, absolutely. This is great for the average user that desires nothing more than just running play store apps. Should you have the ability to run what you want on your phone, and copy the data from the app that you install…

>Should you have the ability to run what you want on your phone Sure, but that doesn't require root to do. The OS can expose capabilities that apps want instead of requiring security to be entirely bypassed with root. >and copy the data from the app that you installed, after accepting the risks? No, because that violates Android's security model. If an app wants to have a authentication token live on a single device…

>It doesn't require root to do this

>No you can't do this at all because it violates Android's security model

You can choose one, and only one, or reject reason.

Re: Android 16 is here

#318

The more I compare Material 3 Expressive to Liquid Glass the more I'm excited to switch back to a Pixel. I'm a fan of the use of color, motions, and different shapes versus transparency, minimal contrast, and little color. I'm on a iPhone 13 Pro Max right now that's still doing well but starting to show battery capacity age. Plus, it's the only non-USB-C device I own so I'd be happy to get rid of it.

This WWDC was the nail in the coffin for me. Apple has lost the plot and is back to self indulgent projects. Picked up a Pixel again and glad I don't have to deal with liquid glass in the future.

I feel similarly. This iPhone is the only Apple device I own outside of a shared Apple TV. I'm not in the Apple ecosystem so moving back to Pixel for me would be easy.

I'm not impressed with Apple as of late.

Re: Android 16 is here

#319

"Samsung DeX has helped maximize productivity on phones, foldables and tablets for years. In Android 16, we worked closely with Samsung to develop desktop windowing, a new way to interact with your apps and content on large-screen devices." PS Let me make a guess for the future. Android Desktop mode will improve and people will ditch Windows and instead plug their phone into a USB-C dock that connects it to keyboard,…

what does this have to do with Samsung? Google just can't make a standard Dex mode on their own?

Re: Android 16 is here

#320
post #87

If Android is getting desktop windowing, how long until I can just plug my phone into a monitor and keyboard and have a usable computer?

It feels like we're getting very close. The recent addition of a Debian VM into Android (I believe it's even in AOSP) leads me to believe we'll be getting Linux apps on Android in the same way ChromeOS gets them. Imagine being able to run VSCode off your phone anywhere you can plug into a monitor. I also think we'll get a more desktop ready version of Chrome. If we get these things I think it'll be a gamechanger.

I already can run vim on my phone. That's enough for me.
Post reply on HN