While building an extension for SABnzbd for Raycast 1, it made me think about a paradigm of multiple UIs. I interact with SABnzbd through its web UI, Raycast, and NZBHydra 2. There may even be another way that I'm not remembering.
The paradigm I thought of from this, and added to my projects list, was something like this:
The name that I gave the project/idea was "headless for everything", where headless is the daemon, in that drawing.
Some clients are local, while some are remote, like "Export to website". There are more and more local- and offline-first projects. What if you could export your data to another service? Chuck some local issues/tickets up in Jira and Linear? What if you could E2E as part of that? What if it could realtime, distributed, and collaborative? 2
The obvious—and huge—downside is that adding a network in-between brings all the issues that a network inherently has. Maybe Photon will help us out.
The Pomodoro technique has occasionally worked well for me. On macOS, I use Tomato 2—and highly recommend it! A Pomodoro timer became the first experiment for me.
The first version used sockets and an SQLite DB with the daemon and CLI client written in Rust. I wanted notifications though and with notarising/signing, I didn't like how I would send native macOS notifications.
The second version got rid of SQLite and kept it all in memory to simplify it and used MessagePack.
The third version, which is a work-in-progress, gets rid of sockets and uses gRPC for communication so that I can write a client in Swift. I did look around, and it seemed possible to use sockets with Swift, but again, I didn't like how I would've had to do so.
While I plan on writing a step-by-step tutorial, in the desire to get this idea and sample out to the world, I've published the repository.
I'm still not decided on Raycast. I would go back to Alfred in a heartbeat if it wasn't so visually dated.
My undergrad thesis was titled Technology-supported activities through realtime, distributed, and collaborative interfaces.