Oddbean new post about | logout
 gm, it’s 2024 neither of the two new trending nostr websites render properly on mobile. https://image.nostr.build/d9c0bd0eda3d79cf520476485ed2b2018ed8fc17858504db9ee302f3b9abe6a2.jpg https://image.nostr.build/f36432dec26968a13b3fef6e827d582548f1609a8bf4801cb7fdb0c64fa91c1a.jpg  
 This is is why you can’t let devs work on things without someone who understands design and UX. 
 If we did that nothing would be released in a timely manner.  Most projects are severely resource constrained and so we get what we get.  9 times out of 10, the "good enough" is going to win out against perfection for every platform. 
 Hard disagree. If there isn’t a mobile-first strategy it’s not even going to be “good enough” and nobody will use it. 
 I would rather have a solid simple program a year from now than a janky one today. 
 Correct ✅ 
 The Nostr protocol actually changes this dynamic because users aren't trapped within a specific app. A higher-quality app can take over the market, even if it arrives much later. 

"Being first" doesn't offer as much advantage, in an open protocol. 
 The transistion from astral.ninja to snort, primal and nostrudel is a big example for that. ^^ 
 Yes, everyone is still frantically racing to be first, rather than considering that there's a new paradigm.

The first project is just defining the second project's new feature, but the second project can build it better by reverse-engineering the first one. 
 I completely agree with this. 
 So its better to not release anything at all until its in tip top shape? 
 No, that's not how it works.

The quality difference comes mostly from setting up a proper architecture and pipeline, at the beginning. There's an initial delay, and then you can release more, faster.

The people who were done first have usually skipped that part because they're in a rush, it's tedious and difficult, and you often need to recruit specialists for the different tasks.

The payout doesn't come until the *next* project, or even the *one after next* when the infrastructure and team is already there and you hit the ground running at high speed, without sacrificing quality.

It's an investment. 
 Bad take. 
 The reality we have, which is a blessing and a curse at the same time, is that the devs we all love are somewhat stubborn. 😅 
 Prototyping is fun, CSS isn't.  
 the amount stuff you can copy-paste from figma these days regarding CSS 
 Rapid prototyping doesn't involve Figma in the first place.  
 seems like refine & reiterate was skipped and deliver phase was pushed https://i.nostr.build/o9wx.png  
 Nah. You're looking at an alpha or beta instance and have set your expectations too high. 
 yeah, gonna set my expectations low for nostr from now on

that's the way for the future? 
 or you can pitch in and help? sounds like they need a QA engineer to help test out their work.  
 QA engineers know code better than i do 
 Useful to have a blackbox tester. 
 blackbox tester? 
 Someonr who tests software, but can't "see into the box". Not knowing how the code is structured leads to different tests.

As opposed to the "whitebox testing" QA engineers usually, do. They're reviewing PRs and stuff, so they aren't approaching with a fresh mind.

Our team has both. Need both. 
 i'd love to test and especially if that is also considered a job, would be perfect

i like trying out new things and finding things do and don't work 
 Then I'm adding you to our list. No take-backs. 😂 
 🤝 
 We only have Alpha or Beta instances, tho. 
 Yeah its a blessing and curse to have early starts.  
 It's just a project management decision.
Every project is free to choose low time-preference development. 
 I see Ben's initial comment as part of the "refine and iterate" process. 

I'd encourage every dev on #nostr to push whatever they're working on live from the get-go, even if it's terribly broken and shitty. 
 it's something i'm 50/50 on

on one hand, launching early, you can get feedback from the community as soon as possible -> faster reiteration

on the other hand -> launching something early, that's not really presentable, you end up throwing off most of the people initially interested, leaving them with a "meh" first impression, and with how big word-of-mouth marketing is on nostr, it's not good for the thing launched. 
 Fair. In my experience most devs launch too late or not at all, which is an even bigger shame.  
 💯 
 Yeah, I disagree.

Most of the stuff that launches is so buggy that people play with it and then drop it, again, and then it eventually stops working entirely and the dev has ghosted.
Encountered abandoned projects seven times this week. Doesn't even surprise me, anymore. Nostr is becoming a gigantic software graveyard.

Diligence is a rare virtue. 
 Whats? 
 This flow is completely completely wrong 
 what flow do you follow? 
 Wiki seems fine on my browser. 🤔
https://image.nostr.build/c538f297667135b9f2cd308391fb0f1420cc9e3d5775b75c53aaa4f7158e724a.jpg 
 safari

how it initially renders:

and how it looks zoomed out: https://i.nostr.build/6Qxn.jpg https://i.nostr.build/BM9Y.jpg  
 Fuck Safari. It is 2024's Internet Explorer. Nothing works on it.  
 safari = ie6 with good design.

there are several sites i use regularly that the search doesn't even work. insane. Chrome, edge, opera, Firefox, kiwi, all work fine. just safari doesn't.  
 But it’s basically the only iOS browser that works with an nsec storage extension. 
 this

i use nostr 99.99% of the time on my phone, as many other of the younger folks do, which i don't think the devs really understand and consider 
 How devs think people will use their products.
https://image.nostr.build/934c3050c9e5ff103fed5da3c8c5d89758b21903bffbc8b29e87a6d661962d20.gif 
 stop making PWA clients for phones before you manage to properly fix the login with nostr part

trying to ride a bike without wheels 
 Is there no nostr browser like spring.site and nostrnet.work available for iOS yet?  
 nope 
 nostr.kiwi i think was smth? 
 Though life 
 The only other thing that works for me is Orion, because you can install nos2x on it, but it only sort of works. 
 Nope. Desperately needed. 
 nsec.app and nip46 login? on iOS you need to go to settings advanced experimental and enable push api, and then install nsec.app as pwa, then it should work and do signing in the background 
 Orion browser exists. 
 Works poorly. 
 Kind of like Safari 😂 
 Like I said, not many good options. 
 Wait. What is the nsec storage called? 
 Nostore. It only works with Safari.

https://apps.apple.com/us/app/nostore/id1666553677 
 Appreciate it 🤙 
 #iFruitcakes 
 💯 
 At least Safari supports ES6. I worked on a project not too long ago where I was restricted to only things that IE supported without polyfills. It was tortuous. 
 Always has been 
 Same on mine https://i.nostr.build/0wvM.png  
 scroll right 
 Login and relays don’t show up properly, you gotta scroll 
 I think i fucked it up, i forked somebody’s reply, said “Yes.” Now it says it’s 38 words and that somebody else said it 🤣 https://i.nostr.build/284X.png  
 Probably some bad cache. Reload 
 I was just thinking this. Nostr is desktop heavy in a mobile world. All these great ideas will be used by almost no one. 
 I don’t think that’s a deal breaker tbh. There are a lot of websites that aren’t mobile responsive, high profile sites like AWS for instance. 
 AWS has an app available. 
 Huge difference between having a split-interface strategy and only having half a strategy.