PremAnjwani

In the early days every new signup felt like proof that we were building something people wanted. But over time I started noticing that signups alone didn't tell us much. Some users created an account explored the product once and never came back. It made me realize that getting someone's attention is very different from becoming part of their routine. At what point did you stop celebrating signups and start focusing more on activation and retention?

One lesson I learned while building a product is that customers don't always want more functionality. Sometimes they just want the things they already use to work together without unnecessary interruptions. A few extra steps repeated manual tasks or disconnected tools might seem like minor issues from a development perspective. But for someone using the product every day those small frustrations can become a reason to leave. It made me rethink how we prioritize product improvements. For founders how do you identify and measure the small workflow problems that quietly push paying customers away?

Most kids' apps we tried as parents wanted an email address for the child, or quietly ran everything on the parent's account.

In TaskyLand a child joins the family with a family code instead. No email for the kid, and the parent stays the one who approves tasks and rewards.

The trade-off we keep coming back to: a code is simpler for a 7-year-old, but it is also easier to share than a login. How locked down should a child's account in a family app be?

How do you handle accounts for your kids today: your own email, a separate one for them, or a family sharing feature?