kylebolt

Great point!

This sounds interesting. Although this use case is very infrequent. If this had a wider use case, like something used daily, that just might be be a viable product!

Yes, no point in more distribution when users were not retaining. Although, it was hard to even get those first few thousand users to try the product.

Yes exactly, having the same app and features on android would still have leave to all users churning like they did on iOS.

Think Clubhouse only moving to android when it was working on iOS.

Well I built it, they came but they did not stay! Would love to know your thoughts on how to validate something for retention.

Stack rank is very underrated as a prioritization tool

This is true, "habits" is too general of a topic. This is why Strava chose cycling as their first sport and expanded from there. Smart of you to focus on fasting, hot topic! Wishing you all the best.

The worst part about a lesson like this is that it can take years to really get to this conclusion. I'm trying to ask myself "who is the buyer of this product". This is happening a lot in digital health where the payor isn't the end user.

We also launched via paid ads (spent around 2k on Apple Ads and FB ads)

I thought habits might be an interesting market to work in + using a chatbot as a novel approach but alas my approach did not pan out.

Good spot, thank you!

Thanks for reading! I'm focusing more on distribution and monetization (or ability to pay) on my next product.

Yes people find it hard to stick to new habits let alone tracking them in an app. Good experience building these things nevertheless.

This sounds interesting, I think the advantage here is that you've focused on 1 use case where I was focused on many habits. Keeping it focused on one niche like journaling makes more sense.

So true, it's an inferior user experience is most all cases where a UI could suffice. (A game product could be the exception)