Key features:
• Native macOS UI using AppKit with some SwiftUI integration (not a web wrapper)
• Core Data for local caching
• Responsive, keyboard-friendly interface
• UX tailored for desktop-class Mac computers
• Supports multiple accounts, cross-instance timelines and search
You can try it via TestFlight (macOS 14+ Sonoma): https://testflight.apple.com/join/Epq1P3Cw
Feedback is welcome here, on GitHub, or via TestFlight: https://github.com/anosidium/Oliphaunt-Feedback-And-Support
OTOH, after you follow both people and hashtags, it feels pretty much like everything else, more or less.
I don't notice "disjointed communities" I just look at the posts from people I follow without knowing which server they are on. I'm aware you can see a list of posts on your local server but I imagine people on most instances (unless the instance has a strong theme like for people from a particular location) never use it.
Do you have any pro tips for optimizing workflow, reducing toil in XCode, or speeding up UI testing?
I can't seem to figure out how to open posts and profiles though. Neither single nor double-clicking does anything. Sometimes double-clicking a post that contains a link would open the link in the web browser. The only thing that works is right click -> open in new window. MacOS 14.7.5 (23H527)
Yes, that’s intentional — to view a thread or profile, use the contextual menu (right-click or control-click). Clicking is reserved for posts that contain a link or preview card, which will open in the browser.
Also, not OP, but I’m glad it’s written in AppKit vs SwiftUI purely; AppKit just feels better on the desktop. I can always “smell” a SwiftUI app just like I can an Electron app.
Unless it's actually SwiftUI taking time to render that UI, which would be bizarre.
As a macOS user I am so used to everything happening in the blink of an eye, so this is something that stands out. It's really not a big problem, 300-400ms.
Was I imagining that wrong?
It’s an AppKit-first app — I’ve used SwiftUI in parts where it fits well, but I’ve avoided relying on it entirely because it’s still maturing, especially on macOS. In certain areas, it can compromise the native look and feel, or introduce unexpected behaviour.
As for Core Data, it’s a proven and robust framework that already does everything I need. Swift Data is still relatively new and doesn’t yet offer the same level of flexibility or stability for more advanced use cases.
Do you write about your experience with macOS dev at all? I would love to hear about it. I still look back fondly on that experience and toss around the idea of revisiting it, Documentation Archive and all.