A UI library is a UI library ser
Discussion
A relay is a relay.
Can’t see how UI libraries can be “optimized” for Nostr
I hear that from :90percent: of devs. Mostly the Big Tech copy-cats.
But Nostr opens up new UX patterns that no UI framework ever had to consider.
- browsing and hopping from content type top content type, 12x levels deep without leaving the app
- an order of magnitude more content types in one app than your typical Big Tech app
- a need for multiple text renderers (especially an inline one that no one is currently putting time in)
- interop ui elements like npub-derived colors
- coherence across multiple new concepts
Anyway I can keep talking and listing stuff... It'll sound ridiculous to most.
When I see a daily driver built with some off the shelf framework that works as a true Nostr notication dashboard + browser, I'll change my mind.
It doesn’t sound ridiculous to me.
Cool
So? That is application logic not a UI library
Call it "A combo of Nostr-based icons + custom content-type emoji + responsive browsing UX components + zap sliders + renderers and parsers for 4 different Nostr based text formats + components that have models of Nostr events as their main input" if you like :winkwithtongue: .
You're referring to implementation approaches to achieve a desired UX. It touches UI, but there's nothing specific to nostr in the UI concerns that would not also benefit other non nostr apps.
As long as “designers” are stuck in the Rube Goldberg machine of prototyping in Figma they won’t know how frontend developers implement designs
HTML and CSS is a very basic skill to learn for a designer, and they can then just use Tailwind to make it easier
Sure it won’t be perfect but congrats you now have something that can be turned into actual website by frontend devs and does not require any tweaking to transfer over from your favorite shitty Figma-like tool
Every job almost always requires a few side skills as well and that is true for designers
Building a native daily driver.
Put torrent on it