Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
blog.timac.org
Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
1–10 of 145 posts
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#2Yup. and basically all apps (re)created suck big time. They're just iOS ports. You're forced to do litereally everything using your mouse, and for example the Home app, it's basically useless if you want to organize/edit things.
We're going to a CRUD operation world, where you have to do every edit one-by-one. And then in a few years, people will be amazed that you can save so much time because of a new "bulk editing" feature.
Ahh such great times with Office in the 90s.
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#3I hate this consolidation of mobile and desktop apps and I hoped Apple would have had the design sense to keep them separate like they should be. Mobile and desktop UIs are two different worlds with different interaction paradigms. Trying to combine them makes an awkward UI that feels good nowhere.
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#4In 2021, the Mac grossed $30B. iPad ($30B) and iPhone ($196B) together grossed $226B. Mac users might think they're still the most important part of Apple but it turns out, the Mac is quite insignificant compared to Apple's mobile OS's when you put things in perspective.
I am still surprised that Apple is pouring resources into the Mac. Nowadays, smartphones and tablets are the main computer for 90% of people. The sooner Apple rebuilds Xcode from the ground up for the iPad, the quicker we can get rid of the Mac with its decades of legacy baggage.
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#5I hate this consolidation of mobile and desktop apps and I hoped Apple would have had the design sense to keep them separate like they should be. Mobile and desktop UIs are two different worlds with different interaction paradigms. Trying to combine them makes an awkward UI that feels good nowhere.
Yup, but you forget the famous "develop once, deploy everywhere" that will give the user "a consolidated experience". And allow you to make huge economy on the cost of development.
At least they don't suffer from the "it's working on Electron and on the web", meaning it will not run any good anywhere. Same result at the end though...
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#6I hate this consolidation of mobile and desktop apps and I hoped Apple would have had the design sense to keep them separate like they should be. Mobile and desktop UIs are two different worlds with different interaction paradigms. Trying to combine them makes an awkward UI that feels good nowhere.
Supposedly a major justification for the continued separation of Mac and the others (especially iPad) was differing UI interaction patterns.
So what are they doing now? Using tools that evolved to serve touch-first interfaces to build desktop applications.
The Mac/iPad split grows more confounding with every iteration. Now it feels like familiar desktop features are being reimplemented poorly in both iPadOS _and_ macOS.
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#7I remember making fun of Microsoft trying to combine mouse and touch in a single UI.
And yet here we are, Apple doing the same thing to macOS, resulting in the same shit desktop/mouse experience that macOS has become.
I understand the reasons but it seems so incredibly un-Apple to sacrifice UX for this.
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#8In 2021, the Mac grossed $30B. iPad ($30B) and iPhone ($196B) together grossed $226B. Mac users might think they're still the most important part of Apple but it turns out, the Mac is quite insignificant compared to Apple's mobile OS's when you put things in perspective. I am still surprised that Apple is pouring resources into the Mac. Nowadays, smartphones and tablets are the main computer for 90% of people. The so…
As a Mac fanboi I wish I could refute your argument, but… those numbers are pretty telling.
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#9It's really not an impressive showing for SwiftUI. 4 iterations later and after being told it's "the future" in unequivocal terms, it's still at 12% (and only like 3% without any AppKit combined (last chart)). It's not dogfooded for any productivity apps. For Ventura, rewriting "Font Book, System Settings, and Tips" is not exactly confidence inducing. If they rewrote Pages or Final Cut Pro, that would wake people up. One showcase productivity app. The thing is, in its current state, I don't they can.
Re: Apple’s Use of AppKit, Mac Catalyst and SwiftUI in macOS
#10I remember making fun of Microsoft trying to combine mouse and touch in a single UI. And yet here we are, Apple doing the same thing to macOS, resulting in the same shit desktop/mouse experience that macOS has become. I understand the reasons but it seems so incredibly un-Apple to sacrifice UX for this.
As someone who literally abandoned Windows for the same reasons (during 8), macOS is still far far from sinking into those depths of depravity yet.