A type of question I see often is "which UI framework is best? SwitUI, UIKit, AppKit, etc?"
And the answer is, of course, usually "it depends" or "a mix, depending on what you need".
I wanted to re-frame that question with specific parameters.
Let's say you were writing Apple Photos for the Mac from the ground up, starting today. For the sake of discussion, it's going to be functionally identical to the Photos app that exists on the Mac today. Which means it:
-
looks and feels like a true, native macOS app
-
should be very performant in terms of rendering and scrolling through a library that may contain hundreds of thousands of photos
-
maintains a large database which can be synced over iCloud
-
etc
When you go to write that first line of UI code, which UI framework are you reaching for, and why? If more than one, which ones would you use for each piece, and why?
Especially interested to hear any viewpoints from Apple folks in this thought exercise!