I agree apps filling up the menu bar is annoying, so there is an option to hide it if you wish.
Point is, it can appear that the OS settings pane/app/whatever is for stuff Apple controls, and the rest has to go in an app or menubar. I'm not saying it's right, I'm saying that Apple has let the messaging get really confused.
Right—part of Apple's job is to create an environment where the "correct path" is clear and developers want to follow it. Either Apple used to do a better job, or else developers did.
And, consider:
• Apple encourages developers to distribute via the Mac App Store as much as possible.
• Preference Panes cannot be sold in the Mac App Store.
• In Catalina, all Safari extensions must be installed from the App Store as individual apps.
• New Notification Center widgets are always installed as applications. Old Dashboard widgets never were.
I would say that taken together, the clear implication from Apple is that apps are the way to go. And it all comes back to the Mac App Store, which Apple wants to push that at all costs. Evidently, they either actively don't want to sell non-apps in the store, or they don't care enough to build that functionality.
There are probably times when Apple's patterns are just wrong and the community coalesces on something better—I can't think of any, but it has probably happened, or will some day. But I do not think this is one of those times, because if you step back, using an app does not make objective sense.
(P.S. It's interesting to note that Apple's own iOS apps tend to have far fewer in-app preferences, in favor of sticking stuff in the Settings app.)
A bit of both I would think. When the Mac was a more niche platform the developer community tended to be more bought into philosophy and design sensibilities around it. And as the Mac has gotten more widespread in popularity, Apple has gotten less good at planning around power-user use cases or communicating how to handle them elegantly.
I still kind of hold Apple accountable for that, though. As the platform grows, Apple has more resources they can dedicate to clarifying UI patterns, or systemic coaching via API design. But they've gone in the opposite direction.
Not true, you can distribute outside of the App Store as long as you sign/notarize correctly.
I think I was getting confused with old-style extensions and the Safari Extension gallery, for which sideloading was truly blocked for around a year.
It’s not even an Apple thing, Windows has been the same for a very long time - remember how browser extensions “exploded” when Mozilla made it possible to write them in JS? IE forced you to C++, dramatically restricting the number of developers.
I'd agree that most of the focus has been on app development, but I just found this toy kernel written in Swift the other day: http://si.org/projects/project1/
On the Objective-C side, sure you have access to all of the low level stuff of C, but Objective-C's message passing is probably a poor choice for very low-level system programming (in the kernel, for example). Apple uses C and C++ in the xnu kernel.
Swift was also designed to interoperate with C and Objective-C APIs, so you could certainly write a preference pane in it. It even automatically generates Swiftier interfaces for APIs that follow conventions. Here's the NSPreferencePane API: https://developer.apple.com/documentation/preferencepanes/ns...
If that was the case (I don't believe it is), it would only be because modern Apple doesn't care enough about Preference Panes to add easy support. A third party Preference Pane is not any more "OS machinery" that a third party screen saver.
An app that does nothing but change an OS setting—and whose user interface exists purely to adjust those settings—does not belong in my applications folder, and certainly not in my menu bar. Such apps ought to live in System Preferences, alongside other, well, system preferences. And what do you know, Apple built a way for third party developers to do just that!
Preference panes used to be the norm, but that seems to have changed over the last decade. It pains me to admit that an app is probably the right approach nowadays, because when everyone else is doing things one way, users will expect you to do that too.
One more way that OS X's UI metaphors have regressed...