How do you decide when a feature needs to be cut?
by•
It is really easy to keep building things users ask for, until one day your app feels heavy and confusing for new signups. Lately I started asking a few regular users which single part of our product they cannot live without, and the answers were pretty surprising. Almost everyone ignored half the stuff we built last year.
How do you guys handle features that barely get used? Do you just leave them there, or do you remove them completely?
1 view
p/runevr
p/producthunt
p/google-cloud-platform
p/aperture-7
p/raycast
p/kuc-kuc
p/lasso-11
p/kodlo
p/ai-context-flow
p/offiai
p/many-displays
p/reso
p/dino-kids
p/dex-by-exmergo
p/supabase
p/jev
p/htmldrag
p/murror
p/nexupira
p/jot-2-0
Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.