> My experience is that you push out the feature and test them. If there us usage, you keep them
There are virtually an infinite number of features you could be developing. But you have finite resources to develop them.
And some features will take a lot more of your finite resources to develop than others.
You need some way to prioritize what to actually develop.
If your product doesn't actually do too much but is essentially just clickbait, then, sure, your features are very cheap to implement, and you just throw everything you can think of out there and A/B test.
There are virtually an infinite number of features you could be developing. But you have finite resources to develop them.
And some features will take a lot more of your finite resources to develop than others.
You need some way to prioritize what to actually develop.
If your product doesn't actually do too much but is essentially just clickbait, then, sure, your features are very cheap to implement, and you just throw everything you can think of out there and A/B test.