Apple declined to implement 16 Web APIs in Safari due to privacy concerns

Re:Apple declined to implement 16 Web APIs in Safari due to ... by cj on Monday June 29, 2020 @09:40PM (#23685596)

I think you’re trying to say that Mac OS or Windows native apps have pretty much the same UI/UX conventions which makes it easy to use any app on that platform. And that Web Apps have UI/UX that is less consistent than apps across OS’s.

I can’t say I agree with this. There are a ton of MacOs apps that implement fully custom GUI (first one that comes to mind is Jira native Mac app which looks nothing like a Mac app I’ve seen before)

I agree web apps are likely eroding OS conventions though. The Jira app is an example of that (they decided to make their native app look and behave the same as the Jira Web App instead of using standard MacOS GUI conventions.

It’s a tough trade off.

[ Parent | on HN ]

Re:Apple declined to implement 16 Web APIs in Safari due to ... by millstone on Monday June 29, 2020 @10:49PM (#23685985)

Yeah and Spotify is another one. Electron is clearly at work here, probably in your Jira example too.

These apps are frustrating for someone accustomed to the Mac UI. Basic interactions (like context menus) don't work at all, or work in unexpected ways. I have no idea what these apps can do because they all have a unique UI vocabulary. So I don't try.

I think Apple has really dropped the ball on this. They ought to have spotted and embraced the web's great strengths early. Ephemeral, zero-install apps, using native components - that's the platform I want. Though I understand how others may disagree.

[ Parent | on HN ]