I have some thoughts on the future of #UI on non-mobile devices and the role that #FLOSS can play.

1. It seems that all proprietary software companies are de-prioritising their desktop OSes, in terms of focus and resources. Microsoft is doing weird tablet hybridisation and Apple is just porting iOS junk back from the iPad.

This creates a vacuum, as there is no modern desktop UI. Nothing's been done since roughly OS X. It's been 18 years. More than my whole adult life.

2. There will be very little financial incentive to fill this vacuum. Desktop OS:es only sell to the enterprise, which has different requirements, and Microsoft has that market cornered anyway.

No-one who is making software purely for money would be able to do this. Well, we, the FLOSS community, aren't, and so we can.

3. In order to do this, we need to experiment. A lot. And most of these experiments will probably fail.

For that to happen, the cost of development in terms of time and cognitive load must go down. Much like Rust seems to have enabled a wave of new command-line tools that are faster and much less boring than the traditional Unix tools. Making a GUI app must be roughly as complicated as making a CLI app.

4. This requires languages AND frameworks. The languages need to remove the incidental complexity in dealing with the concurrent situation that is a modern UX app. The frameworks need to encapsulate common patterns and remove boilerplate.

The languages are mostly there, I would argue, and the patterns are somewhat implemented (functional reactive programming, Excel, etc), but the frameworks are not just a little behind.

5. We also need to train FLOSS people in design AND recruit design-oriented people who may or may not code. This might also entail developing our tools for communication and infrastructure to also capture common workflows in design. I don't know, I'm not a designer.

@albin Agreed. We do experiment a bit, i.e. GNOME 3, but then that generates a lot of heated discussions etc.

I think we have fairly decent desktop UIs now. They should keep evolving for sure, but what we should focus most of our energy on is a Mac like developer experience for desktop aps, i.e. developing an unified set of APIs with lots of complex functionality prepared as part of a SDK for developers to tap into. On Mac, there's AppKit, which is why all the independent desktop apps are Mac.

Follow

@MatejLach we're working on exactly that in GNOME. Builder and Flatpak in particular are big parts of this work.

@albin

@mathieu I saw, and I'm looking forward to seeing the results. Do you also work with the KDE people on this, or do they have their own version?

@albin KDE is working on Flatpak as well: they have their own runtime to build/run their applications, and their "software center" (iirc it's called Discover) can install/update/remove Flatpak apps.

I have no idea what else they are doing, you'll have to ask them. 🙂

Sign in to participate in the conversation
mstdn

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!