Builder’s dilemma: to build more features or not.
More features does not mean better product. In fact, in many cases you want to have fewer, with more focus.
But, the product could be one feature away from being truly unique and interesting. You won’t know what that is until you build it.
What do you do?
Hard one for sure, your are damned if you do or damned if you don’t. Some thing may work well, some may destroy your product. A/B testing can be one way, but you have to build it anyway 🐶🐾🤷♂️🤷♂️🤷♂️
Throw the proposed feature in beta and see how users react
(this obviously means you have to build it but doesn't need to be production ready)
Fuck it. Build it. You can remove features that aren't used and add clutter later on.
Come us with a name
Provide a credit for devices and you manage to get into account the expense.
We’ll write up the uranium suit expense as well.
nostr:npub1ywexl63gwqxdrchr4zkv5hzytsm6hzdv4t25ngmd2r5up6c0tqrq5vw8q0
nostr:npub128futper6qxm0ykcxeshsyczrv8hjx8ctxwanzdde97nduc0u5yq42kj3d is eager to mars, so guess when mentioning the postal service failures things will catalyst.
Or y’all go flying fireworks to the moon and see how that feels.
Build it, then you’ll know, but be prepared to ditch it and go back if it turns out to be elaboration rather improvement…
I like Alan Kay's idea that "simple things should be simple, complex things should be possible." I think this translates into adding features in such a way that the main use case remains simple and unencumbered
Build the features in. Give it to a selected group. See what works and what not. Take out what doesn't and move to the next problem
Gotta be ruthless with features. Kill em with fire till they rise like a phoenix from the ashes as a clear part of the vision and passion. 🔥
Keep developing features and test with a beta group?
What I'd like to see is a consolidated website with all app info linking to those apps AND to a site with their individual features.
e.g. nostr:npub1de6l09erjl9r990q7n9ql0rwh8x8n059ht7a267n0q3qe28wua8q20q0sd keeps talking about Kieran's additions to #zapstream e.g. muting (mute button) is now a thing and, nostr events embed but a) I only know because he mentioned it and b) I don't know how-to.
But maybe that site exists and I have missed it because there is no good entry to #nostr IMO.
Know what I mean?
Ask the users. Do they want it? Do they need it? Will they scream at you for not doing something else instead?
Also you must know your position on the market. If you are a big fish already, working on optimalizations most of the time is likely the way to go.
If you are still trying to acquire your userbase, more aggressive development of new, possibly attractive features might be what puts you on the map.
Still, asking the users is very cheap and quick.
Sometimes you don't need to ask the user directly because it is easy for them to say 'yes, I would use'.
Instead, you can place a button or menu that could drive to the feature and when clicked present a page saying 'the feature is under consideration, click for the waiting list and you will be first informed when it is available'.
As you will be monitoring the click and registering rate, this is a cheap, fast and reliable way to test if your users are really willing to use the new feature.
What you don't have, doesn't break. ;)
