151–160 of 360 posts
Are they still moving forward with killing AOSP?
Where did you get that idea?
- Google will develop Android OS behind closed doors starting next week: https://news.ycombinator.com/item?id=43484927
- Google will develop the Android OS in private: https://news.ycombinator.com/item?id=43482798
It's reasonable to think Google is choking AOSP.
I remember my first android device, it had like 512MO of RAM (and storage), and it was blazing fast, it could be used as a WIFI repeater too (which is why I still have it, although it 2.5G...). Fast forward 13 year later or so, if your android device doesn't have at least 8gig of RAM and 64gigs of storage, then it's pretty much useless given how bloated the OS (and the apps) have become... So basically, Android low e…
> I tried a few Android cheap phones recently IMO that's the big 'problem' with Android - any fly by night company can make a phone with it, which sours those people on Android as a whole and rightfully so. They may not understand that it's not Android itself that is awful, but the low spec'd phone or 'enhancements' some company added. Higher end Android phones generally don't have any of these problems at all. I can…
Force phone devs to use worse phones.
I 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.
I wouldn't judge the new Android until I tried it on a phone either.
Earlier 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?
https://developer.android.com/about/versions/android-4.0-hig...
Earlier 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).
Ex: a.fn-link { padding:10px 18px; margin:-10px -18px; }
I 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.
The notification feature looks nice. I've pretty much exclusively used iOS, but honestly notifications is a weak point for iOS, in my opinion. I frequently have the 1 notification on my home screen, but once unlocked notifications are pretty much impossible to find again.
One extremely disappointing thing that Android has been getting under the hood with Google images is ... Play integrity. This used to be a relatively simplistic system with three tiers: 0 - you are not certified for anything 1 - basic integrity, you need to have a genuine android device running google play services 2 - device integrity, you need to have a genuine android device with core requirements on play and no r…
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. But I do think it would be nice if Play Integrity would expand beyond just Play Protect Certified devices, to devices which can prove they offer a similar or greater level of security.
Earlier quoted context omitted.
Couldn't agree more. Quite a fall from grace by Apple.
Apple did skeuomorphism really well, which is hard and requires a lot of design work. I cannot understand why they gradually abandoned that, as it was clearly a competitive moat in terms of usability. I've seen how computer illiterate or elderly people were able to navigate skeuomorphic designs with relative ease. Right now, they can't tell what is a button or a field and what isn't.
You'd think this is just a little thing, but it can really mess with you if you need to change focus and - of course - every application will 'haha!' you in a different way.
It has nothing to do with skeuomorphism really, but at least skeuomorphism seemed to give everyone an idea of what they were shooting for at least.
It's deeply disappointing to see that the multitasking solution for tablets that Google and Apple have settled on is... desktop-style floating windows, but without workspaces or window snapping. There's so much space here to experiment with tiling views, scrolling columns of windows, whatever. Floating windows are cumbersome enough when you have a mouse and big display to spread things out on. I've tried this floatin…