Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I switched from Android to iPhone last year, and this just isn’t true. There’s so many tiny issues with android apps that just don’t exist on iPhone, because the android apps have to work on all these different devices. You don’t even have to look for the kinds of apps you’re talking about because things like Safari and Apple Podcasts work really well. I know people have a lot of complaints, but things on the iPhone really do “just work”.


iOS is great if you only want the parts that "just work", and don't need any of the things Android has that "just don't work" on iOS.


> because things like Safari ...work really well

Are we living in the same universe? We manage a fleet of tablets (both Apple and Android) for a healthcare company whose EMR is web-based. And because of that Sarafi has made our lives miserable. So much so that we're migrating to Chromebooks.

I've been developing for the web for 15 years. The first half was spent battling Internet Explorer. Now it's Safari.


There are some proprietary Chrome APIs but if you’re not using those it’s been pretty rare to have major problems in recent years. I open a couple of bug reports a year against Chrome, Firefox, and Safari—mostly accessibility related—but most of the time it’s been a problem with code written specifically against Chrome rather than code which couldn’t work in the other browsers.


The people complaining about Safari often are running enterprise crapware that requires some esoteric Chrome API or bug to operate correctly and should actually be an app on iOS but cannot be funded as such because its creators don’t care about its users.


Then again, if a company can't polish a web browser app, then the native app they'd produce will be even worse.

Now you have a crappy app that only works on some devices, and now with no tabs, no links, text you cannot select anymore because they used the wrong component, etc.

Ugh.


Well, formerly you would have been right, but WebUSB and whatnot are gaining a lot more traction.

I didn't take WebUSB seriously until I steered someone to flashing a small firmware onto something and they could do it straight from the browser! And it was a nice workflow too, just a few button and a permission click.

Two other examples I can think of are flashing Via (keyboard) firmware and Poweramp using WebADB via WebUSB to make gaining certain permissions very easy for the layman. I imagine it's gonna get more and more user in enterprise too.

Firefox is seriously behind by refusing to implement it.


WebUSB is a giant gaping hole in the browser sandbox. Innocent use cases are really nice, I've used WebUSB to flash GrapheneOS on my device, but the possibilities for users to shoot themselves in the foot with nefarious website are almost endless.

Consider the fact that Chromium has to specifically blacklist Yubikey and other known WebAuthn vendor IDs, otherwise any website could talk to your Yubikey pretending to be a browser and bypass your 2FA on third party domains.

I'm conflicted on WebUSB because it's convenient but on the balance I think it's too dangerous to expose to the general public. I don't know how it could be made safer without sacrificing its utility and convenience.


It really isn't. Chromium (since 67) does USB interface class filtering to prevent access to sensitive devices. Then there is the blacklist you mentioned.

On top of that, straight from Yubico's site:

".. The user must approve access on a per website, per device basis .."

This isn't any more a security hole than people clicking "yes" on UAC prompts that try to install malware.


> ".. The user must approve access on a per website, per device basis .."

Of course, but a phishing website "fake-bank.com" could collect user's username, password, and then prompt them to touch their yubikey. This wouldn't trigger any alarm bells because it's part of the expected flow.

> This isn't any more a security hole than people clicking "yes" on UAC prompts that try to install malware.

Yes it is. The only reason why Yubikeys are immune to phishing and TOTP codes aren't is because a trusted component (the browser) accurately informs the security key about the website origin. When a phishing website at "fake-bank.com" is allowed to directly communicate with the security key there's nothing stopping it from requesting credentials for "bank.com"


Again, that exploit factor is irrelevant now because WebUSB is blacklisted from accessing, among other things, HID class devices. So no site, even with permission, can access U2F devices over WebUSB. There is no special blacklist needed per vendor or anything.

You are right that it was a security hole in Chrome <67. Which is almost a decade in the past by now.


> some esoteric Chrome API or bug

Or simple things like supporting 100vh consistently. Is that estoric?


I’m a developer too, but the developer experience doesn’t matter to users. As a user of the app, it’s fast enough, cleanly designed, seems to be reasonably private and secure, and I haven’t hit any website with it where I’ve had to download chrome to view it or something.


You're a developer but you can't connect the dots between features being hard to build and the inconsistencies between other browsers vs Safari to how that might effect the user?


I can be a user separate from being a developer. The user experience of Safari is basically perfect for a browser. The development experience is completely irrelevant from that perspective.


> The user experience of Safari is basically perfect for a browser.

This is such a wild, absolute statement it's not even worth discussing this with you anymore.


I mean… what do you want me to do, list problems I don’t have with it? As a user of the app, Safari fades completely into the background for me, I don’t know what else I could ask for from a browser.


> I know people have a lot of complaints, but things on the iPhone really do “just work”.

Recently on HN: https://www.bugsappleloves.com/


I would love to see a site like that for android, but people don’t have the same expectation of flawlessness with it.


I've tried switching to iPhone and the lack of a consistent back button like Android has always drives me crazy.


> but things on the iPhone really do “just work”.

For values of “just work” close to 0.

Make a picture, connect with a Windows PC, iOS needs a password, then the picture is not visible to the PC, disconnect, go with Apple photos to look at the picture, repeat connecting, with password, now it is visible.

Try to set up a hotspot, there is no button to turn the hotspot on/off.

So yes, it “just works"


You can find your hotspot button in the control center. Swipe down from the top right of the screen. It’s in the same section as airplane mode / WiFi / cellular data, and takes another tap to access.


You actually don't even need to set up hotspot more than once if the phone and the computer are both yours (and apple-brand). You can just connect to the iPhone with the Mac (if they're on the same iCloud account) and it works without entering a password.


> Try to set up a hotspot, there is no button to turn the hotspot on/off.

There is. You can even put it on the settings drawer. Look for "personal hotspot".

I don't have a mac anymore, but IIRC you could even turn it on from the paired mac. This definitely still works between iphones. When I take out my old iphone from the drawer to use as a GPS on my bike, with no sim card, it will connect to my regular iphone's hotspot automatically.


> Try to set up a hotspot, there is no button to turn the hotspot on/off.

I’m confused, which button? Do Android phones come with a physical button to enable hotspot?


Just a quick shortcut




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: