First thing that came to mind is using Nostr as a way to seed/sync settings when setting up a new device with Omarchy.

The interoperability is also a cherry on top of an app in my eyes, not a leading feature itself. It works well as a secondary thing to discover after using an app for a while, so making people be aware of it doesn't add much value unless you're explicity looking for something with interop in the first place. It might just serve to confuse users with needing to learn about Nostr if it's front and center.

Current longform clients are clunky for my preferences to use, but I've been meaning to turn my website into a Nostr-backed site, so natively going forward they will be posted on Nostr when I publish them.

Agreed, it can't be thrown out in its entirety. Social has some useful primatives (like following lists and the social graph), but interfaces focused on social-first experiences are a lost cause.

I see social-last at a UX level, not a protocol level, meaning users are only exposed to the minimum viable social features required to make discovery and communication in an application seamless via the network. The social UX landscape is not something I think Nostr should be focused on adopting or competing within.

I've heard of over 10x savings. Might just be my prompt style and usage.

Exciting!