Android 12
android.com
android.com
>Any information processed in Private Compute Core requires explicit user action before it can be shared with Google (...)
If they know everything about the data going in and coming out it's still useless.
Also what important APIs did they axe now?
"Ask HN: Do you still miss your RIM BlackBerry?"
But otherwise I do agree it was a fantastic phone for easy communication. Although it was far too easy to txt and drive
I'm no fan of the current whitespace-heavy UI paradigm, but to say BlackBerry did it better is definitely not matching my own memories of my BlackBerry devices at all.
some of those list items took some action immediately, some opened further lists, and there was no differentiation visually, for example. some may call that "tool-like", but I call it "lacking important contextual information", and it's just as bad as other UIs which lack important cues.
> modern smartphone tries their best to be hostile toward their users no matter what
they definitely do not try to be hostile. I sense an attitude on this site lately which is probably best summed up as "everything new is stupid" and that is just as misguided as believing that modern smartphones are intentionally hostile.
MAYBE they're unintentionally hostile. Maybe, but I doubt it. Smartphones are imperfect, yes, and dark patterns DO exist, yes, and I can't recall ever seeing anything hostile in Android or iOS or iPadOS, ever. organized poorly? sure. oversimplified? yep! hostile? never.
By your logic we should be able to use a PDA interface on a smartwatch.
Don't you think that a letter is a bit optimistic? What about colored buttons with icons, ala Idiocracy?
I don't think fashion has an endgame.
I almost cut my arm off with all that edge. Care to dial it back a bit?
The counterpoint is that most of the 'information' apps think are important really are wasting my time and obscuring actual signal. Putting design on a diet and making apps think about what data is priority vs noise is something that respects the user.
The ability to glance at my phone and get the most important info without parsing out noise - that's a big plus. The ability to mix and match widgets on my home and lock screen to display the data I want without crowding stuff out - also great.
It's funny that a related argument against mobile is that all apps demand full screen and it's difficult to do advanced work bc of app switch friction - well this approach of forcing apps to limit and prioritize info puts out a path of addressing that inefficiency nicely.
> what important APIs did they axe now?
Again many API turn downs improve user privacy, improve system stability, or push apps to more battery/memory efficient APIs.
Do you really want win32 level of API compatibility? As a user I don't care. As a developer I would rather work on a living and evolving platform then a fossil or legacy tarpit.
Just playing to their customer. As time goes on, the demographics of Android users get older and less savvy as everyone else switches to iPhone. (not snark, I have a Pixel myself)
They did this. It’s trendy. Later they’ll “discover” information density and go in the other direction.
Its really the getting old denial mode. All of those people need reading glasses not huge font. Seriously the in house attorney where i worked(like 70yo) had his phone font set so large it was like 2-3 words per screen on email and text.
I used to know this stuff, but these days couldn't care less.
For me smartphones are just good enough.
They all take nice pictures, they're all fast enough, they all have a nice screen, nice touch controls and nice UI.
It just doesn't matter as much anymore.
The only thing on here that made me go "oh cool" is the extra dim mode, my 4a really likes scorching my retinas at night.
a. A better quality of pictures even in less-than-perfectly lit scenes. This matters indoors or in the gloomier months of the year.
b. As you mentioned, an extra dim, or on the other hand extra bright, mode of the screen. Trying to orient yourself in blazing midday sun is a horror with some screens.
c. Fast charging is something I thoroughly enjoy.
Also, given that they have translation and live transcription of videos, live translation of videos was the next logical step. I hope it's available for all audio sources.
IMO, one of the recent updates brought nice feature to AOSP and therefore all vendors: navigation via swipes.
I wish google patched their devices for longer, I'd happilly only update every 5-6 years these days, but security doesn't allow for it.
I guess floating notifications, but even that is meh. Facebook had those annoying floating faces 5 years ago
I do remember when they were trying to push touchless gestures (e.g. changing the spotify song by waving your hand) which is a perfect example of a feature that pretty much no one wanted. I imagine google had to pay spotify to include that feature. Needless to say
I went back to my trusty old OP3 running Android 9 I think, for a bit, and the overall experience took a hit. Everything felt kinda clunky now coming from Android 11, even though I always loved the clean Android implementation of the OP3.
Mobile OSes are mature these days, there aren't as many (or any) opportunities for sweeping changes that improve the experience. These days I almost dread Android updates because I don't know what they're going to change for no reason that breaks my user flow.
You know what? You’re right. It sticks out like a sore thumb because it’s so different from my normal experience. I’m used to some 3rd party apps being terrible but not the OS itself.
(Never used Android for more than 5 minutes, can’t comment there)
"Oh, yeah, that's cool I guess. Be fun to get to use it in five more years when enough people have this, or a newer, version, for it to matter."
A few years ago the phone co's would sell a phone today to your parents that was already 1-2 version behind especially if the phone was released a year or so ago. And then NEVER update it over 3 years outside of (maybe) some security updates.
For some reason, a month after iOS is released, phones from Apple, including older phones still being sold, are either sold updated or can be updated.
That reason should be pretty obvious. Apple has a massive profit margin on their phones, so they're economically able to do this.
The margins are super small with Android devices, so if any OEM tries to offer support they'll be quickly undercut by the competition
Meanwhile my iPhone 8 got iOS 15 over 5 years after it launched.
iOS 14.8 was 9/13/21 14.7 was 7/26/21
iOS 12.5 was 6/14/21
So that's 7+ years?
Widgets, as well, have been a deal breaker for me, what makes you dislike them?
The only real problem I have with iOS as a whole right now is how buried some actions can be, especially in apps like Safari and Music, some things which should be a press away can take 3-4 taps to complete, which while not really annoying does make me feel like a grandpa just tapping away at his phone to share an image or add a song to my queue.
The shock of the move from 6 to 7 was pretty large. 6: "slide to unlock" slider that looked like a physical slider-latch, like one you might slide to unlock a container, and was so obvious in what it did, that it hardly even needed text to be usable by anyone. 7: "swipe to unlock" in thin text on... the background? So what do I swipe? Oh, the screen itself, which is a completely different metaphor for interaction, and entirely unintuitive to people who don't think like that. That kind of thing, repeated across the entire UI.
Most of the multitasking stuff they've added, are just weird modes I accidentally put myself in then have to spend time figuring out how to get out of them. I'm sure they're pure rage-inducing hell for most people, who are even worse at tech than I am.
I think the loss of the home button, one of the most brilliant UI elements of all time, is a big loss for intuitiveness/usability for people who aren't immersed in very digital-native metaphors. It was such a great safety net for people. "Oh shit, what's this?! HOME BUTTON! Ah, now I'm in familiar territory". Swiping the screen up from the bottom is not a complete replacement for that.
Overall it's just far less relaxing and straightforward than it used to be. Used to feel like some kind of hyper-advanced "slow tech" sort of thing. Now it's a lot closer to just being another computer OS. I wouldn't care, except there's no alternative that provides the old thing that I liked better.
> 7: "swipe to unlock" in thin text on... the background? So what do I swipe? Oh, the screen itself...
I can already detect what is probably a massive difference in technical literacy and age between us but I'll humor myself anyways. I still have an iPhone 3g lying around with the old physical looking slider and while i do agree it made more sense than just swiping up from the background, our great UX overloads at basically every phone company around the release of iOS 7 probably decided that just swiping on the background was more aesthetic and "modern".
Now that I think about it, the same could probably be said for just about any major mobile UI change over the past few years.
Also regarding what you said about the move from a physical home button, I am torn here, I like both approaches very much (as someone who has an iPhone SE and a 13 mini on hand) and can't really decide which is better. Though I will admit that once you really master the fully gesture based UX of newer iOS releases, it is just a tad but more efficient, if less "sensible" overall.
I still do wish Apple made a flagship alternative iphone which was just an 8 plus but with the latest and greatest chip and screen and battery and whatnot but with classic old look and feel, I have no doubt it would sell pretty well too.
> Overall it's just far less relaxing and straightforward than it used to be.
I genuinely believe this is by design, these products (both software and hardware) are being sold to people who already know what's been going on for the most part (and in the case of newbies, this is what they are first introduced to so they never even knew there was another reality) and can easily adapt to the new interface changes. In practice, I remember people being frustrated about the iPhone X's gesture based interface but Apple has improved it to the point where no one really mentions it anymore, it's just a part of the refined iOS experience now i guess.
> Swiping the screen up from the bottom is not a complete replacement for that.
Last note, you have to at least acknowledge that it's mad satisfying to do so, if a little unnatural at first.
Rightmost screenshot: wow, iOS and Android quick-settings screens have converged a lot more than I realized, since I was last in the Android world. Who copied whom?
It's really weird that the rightmost screenshot (the quick-settings screen) bumps the top bar down for a second top bar that just prints the date, in small type.
The permissions and privacy stuff seems OK but I'm surprised they were so far behind on that front that this is new.
Screenshot interface is also damn near identical to the one on my iPhone. Again, dunno who got there first, or if it's just convergent design... but wow, it's very close. The "scrolling screenshot" thing is cool, though I wonder how that'll interact with drawing rules for various app widgets—or maybe it just works on web content? (no clue if my iPhone can do that—I don't think so?)
Phone switching feature—again, I'm surprised this is new for them. Being able to do it from iPhone, too, is a nice touch though.
The feature itself is very old. I think they are implying that in previous versions it did not transfer all your "essentials" and now it does - it isn't really clear to me what exactly they improved, though. And the iPhone bit may be new.
sounds like a privacy thing
It's a weird choice for a bunch of reasons—why go to extra effort to print the date on the settings screen, of all places, but not in any kind of a "you can edit this here" context, but only an informational one? Why not find a way to put it on the existing top bar? (it looks like there's room, even with the notch) Why break a "this bar is fixed at the top and doesn't have anything 'above' it in the view hierarchy—all it might do is disappear, not be pushed down" norm for such a minor thing? If you're going to that effort, why only use like 1/4 of the width (even accounting for the notch) that you're claiming, and not display more stuff there? Why not just print that under the existing bar, if you've decided it needs to appear on this screen?
It looks like a mistake, as is. Like some kind of temporary dev UI element that got left in by accident.
/s
Not really, I live in Croatia (EU member) and the product is not available in my country.
Not all shops will ship abroad, but buying a smartphone shouldn't pose a problem.
But Google will tell you they are not in your country, they won't ship there and you can just look:
> We aren’t in your region yet > > You can still browse our products in any of the other regions.
Google could just enforce it, like they enforce so many things, by tying it to the Play Services license. If Google wanted to prevent manufacturers from 'customizing` (ruining) their Android phones, they could do so.
seriously, "adding value" has never once "added" any "value" for the end user. not once.
Oh, come on.
Because I wanted to read what they meant by
"With new easy-to-use, powerful privacy features, you’ll have peace of mind"
but noscript blocked any link or something.
"If you see anything that you’re not comfortable with, you can manage permissions right from the dashboard."
I doubt I can remove all permissions from Google (?)
The next four sections expand on it: see what apps are using the mic and camera, option to give apps only approximate location data, app permissions dashboard, and the local computation for some data.
https://www.theverge.com/2019/8/22/20827231/android-10-q-goo...
It doesn't really matter, but it's weird reasoning. Cutesy touches like the dessert names help humanize tech company products and anchor them in reality. It's a shame to give it up because we can't find universal desserts, which is a strange claim to make anyway -- wouldn't anybody, anywhere, appreciate a marshmallow? Why not pick some foreign desserts from unappreciated countries to bring attention to them, instead of abandoning the concept entirely?
Doubtful. Cacao farmers have never tasted chocolate [0]. Foods and desserts are not universal. The sugary slop I eat in America would be appalling in many places across the world. Not to mention the portion sizes.
[0]: https://www.npr.org/sections/thesalt/2014/08/01/336919715/th...
...but when exporting, we have to sanitize cultural expression so as not to confuse or offend.
This is all a bit silly.
Whats wrong with just taking random foods from around the world?
OS X names used to be big cats too until they ran out of good ones. Now it's locations in California. Who knows what it will be next.
Upgrading Android phones, even with their supposedly new migration assistant via cables, still kept losing most of my apps' device-local data and settings, as if Google didn't care about anything that isn't on their servers.
On Android, all of my photos are backed up to Google Photos. Most games use Google Play's cloud save system. All of my notes are in Google Keep or Google Docs (or Notion) which all are backed up in the cloud. Whenever you switch phones, you can easily select a list of all the apps you want to install and _most_ of them have data backed up automatically.
I think literally the only stuff on my phone that isn't backed up is local files (downloads etc.) but those could easily just be saved to Google Drive instead of on-device.
And besides downloads, there are many apps that just use local files and that you therefore need to transfert manually. e.g. apps from F-Droid, SMS, Wechat, etc. So even though "many" stuffs are automatically stored in Google servers, you still need a lot of case-by-case manual attention and care when transferring to a new phone.