Nostr Web Client

For this to work you probably need more thorough vetting too.

One year with Nostr should be more than enough for a good product. But I don't think it is enough for monetization of that product so that the dev team becomes self-funded.

Too buggy

That's less of a funding issue and more of dev quality. Funding alone doesn't solve bugs.

No but time does. And nobody wants to work on bugs on an inherited project.

I don't know which project you are talking about, but yes, devs don't like project inheritance.

However, time also doesn't solve bugs. Most bugs are quick and easy to solve. But also nobody wants to do work on solving bugs.

I’m avoiding naming anything on purpose but it applies to many projects, some more than others.

Are you sure you’re looking at this without bias? Something tells me you’d be working on nostr with or without grants without worrying about money, which I can’t say about other devs who are replacing their income.

I have resources, but not as much to do this without any income.

It's hard to make an assessment on the bugs without knowing the project, but I can guarantee you that many (majority of) devs are not cut to finish projects, regardless of payment. If they spent one year and can't get a good-enough product out, where most users can use in inspite of the minor bugs left, money wasn't the issue.

I have good examples to support my point but I don’t want to single them out. Respect your opinion 🙇‍♂️

Interesting. I am glad I am not in any review committee :)

Water Blower 1y ago

I agree with nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z in a painful way. My previous project Blowater was a failed attempt.

It’s not a time or funding problem. But a skill problem. But not just normal skill problems like programming or designing.

They were about meta skills such as “how to ship a product” and “how to plan a strategy”

Most indie devs were like me who only had worked as a specialist.

The meta skill can only be learned by doing the thing for a long time. Maybe it’s just hard in general for novices to achieve things independently.

If you had to start a new one what would you do differently this time?

Water Blower 1y ago

There are many things. Start with:

Design the thing first instead of hacking right away

By designing, I mean both graphical design and software design.

Implementation is the easy part. Code is just an artifact. Don’t measure the progress by the size of code. Measure by user activities.

My biggest mistake is building a "super client" which have many features, the more features the more bugs. No ways to handle it as solo dev.

Ya smaller scope project is better imo. For the reasons you mention but also easier to see if there’s demand for it. Larger scope project requires more time in the market for pmf.

Many nostr devs think bigger projects are the secret to monetization. They are wrong.

Yes, I thought like this before. So when building coop, it just focus on chat, not event have groups yet.

Agree. I don't event think a good chat client needs groups (outside of the small group spec of NIP 17). I believe groups will be better managed in Discord like apps where you have workspaces to split them up.

Yes, I thought like this before. So when building coop, it just focus on chat, not event have groups yet.

TKay 1y ago

That’s why things like Olas will be huge.

One feature apps will be amazing.

I am not even sure Olas needs to support video shorts. I miss the old Instagram with just pictures and nothing else.

Yes, I barely use the video shorts on instagram, the video is too short to have meaningful content 🤣, just girls doing some retard dances.

Jalmoud | جلمود 🇵🇸 1y ago

I agree to this too. At some point everybody started copying everybody, and we ended up with Frankensteins.