things i realised while developing Memestr_app (npub14a3…ejtd) for last 8 months on nostr.
one thing i have realised.
- Not a lot of dev resources online other than GitHub read me and handful of very basic videos.
- Telegram groups are your most accurate source of information.
- By the time you get hold of NIPs and get busy developing your app, either new NIPs come out or previous implementations change without any major announcements. unless you are actively monitoring nostr social feeds, no specific newsletter you can subscribe to mentioning the changes in NIPs you are interested in.
- Help is hardly available. No volunteers, No major Sats contributions, cant run ads. Even if there is no backend, hosting relays or creating something meaningful is gonna take a toll on your pocket.
- Community is helpful. Some people really love to test your ideas and give suggestions (like Karnage (npub1r0r…q9ac) ) but otherwise, its you and your own vision of a service.
Overall, No guarantee of if its gonna work out in the long run or not.
Creating on nostr is supposed to be more fun. That’s why we are creating on nostr and not a centralised API driver another app like billion others. However that really seems to be getting tougher and tougher.
I do not wanna lose hope. Some apps really have made their names and i feel glad everytime i see a new app rocking on nostr and utilising its potential to build cool features. however, it seems i took a bite bigger than i could chew. I am not gonna stop though. Even if the chewing takes longer, i am in it for the long run.
When has it not worked in the end after all right?
#HappySundayNostr.
sarakeshtix
npub1zu…zpl4x
2024-04-28 05:27:04
Author Public Key
npub1zumzudhtu2558fgvycnjlc7pq9l4m338vghgcfzafftz9qg45ruslzpl4xPublished at
2024-04-28 05:27:04Event JSON
{
"id": "98dd5427cb7534165645ef38ef28d9edeedff3687d056f97bbced4be7786da1c",
"pubkey": "17362e36ebe2a943a50c26272fe3c1017f5dc627622e8c245d4a56228115a0f9",
"created_at": 1714282024,
"kind": 1,
"tags": [
[
"p",
"af630aeba7d8cf6e8cade31226a9023c26b91b04b3a1f218f56a6793244968ae"
],
[
"p",
"1bc70a0148b3f316da33fe3c89f23e3e71ac4ff998027ec712b905cd24f6a411"
],
[
"t",
"happysundaynostr"
]
],
"content": "things i realised while developing nostr:npub14a3s46a8mr8kar9duvfzd2gz8sntjxcykwslyx84dfnexfzfdzhqz4ejtd for last 8 months on nostr. \none thing i have realised.\n- Not a lot of dev resources online other than GitHub read me and handful of very basic videos.\n- Telegram groups are your most accurate source of information.\n- By the time you get hold of NIPs and get busy developing your app, either new NIPs come out or previous implementations change without any major announcements. unless you are actively monitoring nostr social feeds, no specific newsletter you can subscribe to mentioning the changes in NIPs you are interested in.\n- Help is hardly available. No volunteers, No major Sats contributions, cant run ads. Even if there is no backend, hosting relays or creating something meaningful is gonna take a toll on your pocket.\n- Community is helpful. Some people really love to test your ideas and give suggestions (like nostr:npub1r0rs5q2gk0e3dk3nlc7gnu378ec6cnlenqp8a3cjhyzu6f8k5sgs4sq9ac ) but otherwise, its you and your own vision of a service.\n\nOverall, No guarantee of if its gonna work out in the long run or not. \nCreating on nostr is supposed to be more fun. That’s why we are creating on nostr and not a centralised API driver another app like billion others. However that really seems to be getting tougher and tougher. \n\nI do not wanna lose hope. Some apps really have made their names and i feel glad everytime i see a new app rocking on nostr and utilising its potential to build cool features. however, it seems i took a bite bigger than i could chew. I am not gonna stop though. Even if the chewing takes longer, i am in it for the long run. \n\nWhen has it not worked in the end after all right?\n#HappySundayNostr.",
"sig": "82aa3a2e5aa891d6792874cfdbdcb65344eb28ef580edab80555032b44e20661916b47e04f14b1f692f486090eb75a7d16194d25a5194640947f4503e2954ba2"
}