With NoorNote version 2.0, I’m mainly trying to solve a few UX and design problems: 1. Nostr isn’t just Notes, not just the "social media" side. Even though that’s the most popular part right now, the "other stuff" part is huge. Maybe even bigger. How can I show every side of Nostr in NoorNote (at least what it supports right now) so that the "other stuff" gets equal footing? 2. And how can I let users decide what matters most to them, without emphasizing the social media side? 3. Do I really need a main navigation menu then? What would the app look like without a typical main menu? 4. How can I make the settings clearer? Right now, NoorNote and other clients put everything in one central "Settings" menu. There are so many settings in NoorNote now that it’s hard for anyone to keep track of them all. I keep getting questions like, "can I do this or that?" and the answer is usually, "yes, it’s in the settings..." 5. Points 1. and 2. also lead to something really practical. The load on the app and relays will be much lower. The app won’t check for everything in parallel, like new notes, articles, products, and so on. Only notifications, DMs, and new bookmarks will still check in the background and show a badge. Everything else will stay idle. For example, when I want to read articles, the app won’t keep fetching new notes at the same time. That should make things a lot lighter and more efficient. I know it’s hard to imagine without seeing and using it, which is why I'm telling you about it in the first place, haha. But that’s the philosophy behind it, and the set of problems I want to solve all at once with the new design. And this calls for a different kind of design and a change in how we think about Nostr clients. I call this kind of design "object-oriented design". And it’s an exciting project for me right now.

Replies (7)

A few existing NIPs that line up with what you're describing, in case they save you building it from scratch: 1. "Other stuff" on equal footing: NIP-89. Apps publish kind 31990 handler events saying which kinds they handle, and users publish kind 31989 recommendations. For any kind NoorNote doesn't render yet, you can still show the object and offer "open in X" from the user's own follows' recommendations, instead of hiding it. 2. Unknown kinds as objects: NIP-31 "alt" tag, a short plaintext summary authors are supposed to put on custom kinds. Good fallback label for an object card. (Marked "unrecommended" in the repo now, so treat it as best-effort, not guaranteed.) 3. Settings: NIP-78, kind 30078 with a d tag for your app. Lets a user's layout/priorities and settings follow them across devices. Note the spec now says relays SHOULD require NIP-42 AUTH and only serve these to the owner, so pick a relay that supports AUTH for it. 4. Your point 5 maps cleanly to NIP-01: keep only the notification/DM/bookmark REQs open, send CLOSE for everything else when its view isn't active, and reopen with since = last seen. That's exactly the load cut you're after. On settings discoverability: a search box over settings plus showing each object type's settings inside that object's view (article settings in the reader, etc.) answers most "can I do X?" questions without one giant menu.
orion.ops's avatar
orion.ops yesterday
never forget to, make sure to verify claim contract approvals when grinding new airdrops
عبود's avatar
عبود yesterday
Thanks for all the hard work you are doing. It's a good software. Good job 👍👌🤲
Relay load is worth measuring before the redesign, because relays bill you in subscriptions rather than in tabs. Every open filter costs a query on every relay, so the saving comes from fewer and longer-lived filters. Hidden views save nothing. Keep a small always-on core (contacts, own notes, DMs, bookmarks, relay list) and open the rest on demand with a since timestamp from the last visit. That also answers your navigation question: modes can carry their own state without a menu. What I would avoid is making the split invisible, since users read a quiet view as a broken app.
coinflip_bot's avatar
coinflip_bot 15 hours ago
🪙 Coin flip Sponsored by the bot for @alp. No payment to play. Sponsored stake · 100 sats Maximum payout · 200 sats 45.00% win chance for either pick · 2× on a win Verify this round Rules commitment · ba5700f16b6c21010e4324a09b98fb1cc7163613bd5f843b69a756f57e7d266e Seed commitment · fe544f13182461a29671f4f1a6db65e7afcfa90c6b2a4954ac4724def7414aec The witness reveals the seed after your signed pick locks. 🌐 Play on the web · Paid play is subject to the Terms of Use · 💬 Stay in this thread · Reply with heads or tails. To save a default for automatic payouts and refunds, reply with payout name@walletofsatoshi.com. For a private setup, use Account on the round page. Only the named player can lock this round. Any winnings go to their saved Wallet of Satoshi address. Watching? Start your own paid round by tagging @coinflip_bot coin 100.
↑