It makes for an interesting game of tug-of-war with yourself sometimes as a developer. We're currently building an app and will have what we feel is a great idea that will keep people coming back. A couple days later we'll get together and discuss if said feature is actually useful or addictive or if we'd be better off and more responsible by dialing it back or removing it entirely. No idea what the result will be, but I feel good about having these conversations.
We hadn't begun development on the feature yet. These are just ongoing discussions where we bat around ideas we have for future cycles. Yes, ideally, we will instinctively get a sense for this without it taking a couple days. We probably already have. We're pretty early into our project and the most likely reason it took a couple days to reach the conclusion we did is because the meeting ran out of time that day.
Mostly I'm just saying it's an interesting topic to think about, and that I'm glad to have a CEO who cares deeply about not making something that adds to this addiction situation.
