pull down to refresh

Format of sharing dev updates
296 sats \ 4 comments \ @NoStranger 30 Nov 2023 nostr
As I'm planning my work for #meetstr, I thought about how to share my development updates.
What do you think is the most effective format?
I'm working on a new Nostr client with its own custom NIPs and I thought of touching different topics with it.
What I'm wondering about is whether I should share something like a devlog with just technical details or to be more open with my thought process and experiments and share tips and tricks for the implementations.
What do you think would work better?
write
preview
related posts
100 sats \ 1 reply \ @k00b 30 Nov 2023
The best advice I can give in such updates is teach us something, ie pay us with learning something new for reading about your product.
The worse advice I can give is do something low effort and inconsiderate of readers and just shill your product.
You get what you produce for.
reply
680 sats \ 0 replies \ @NoStranger OP 30 Nov 2023
Absolutely, maybe making those updated feel like little tutorials could help a lot, the code would be open source anyway so there's nothing to hide, but just explain what and how it's done.
Thank you for the advice!
reply
20 sats \ 1 reply \ @0xbitcoiner 30 Nov 2023
I think it depends a bit on the audience. If the audience is more of developers, it might work better to present more technical information with some tips and use cases.
reply
10 sats \ 0 replies \ @NoStranger OP 30 Nov 2023
I'm thinking of mainly sharing on bolt.fun so there are other creators there.
Maybe I should split it, devlog there and quick end-user focused updated over Nostr.
reply