TL;DR: A busy week. We fixed our idea Inventor, built a new research agent that maps user journeys, and set success metrics for Dream Jar. Apple approved our business account, so Dream Jar goes out to friends and family for testing next week.
For the last two weeks, the quality of our Inventor's ideas had dropped. I had tweaked it to screen out ideas that might be too crowded or too easy for AI to automate away, and that screen made its ideas worse. I learned that it doesn't need to get the exact product right. It's most helpful at spotting big opportunities: where people feel the most pain and frustration. So we walked back those self-filtering instructions.
Another thing I realized: the consumer market is already crowded with apps that solve pain points (obvious, I know). It reinforced my belief that creating delight matters as much as solving problems. Our engineering brains easily latch onto solving problems, but solving problems can feel scarce, creating joy and delight feels abundant.
We built a research agent that takes a product idea and maps out the user's journey, step by step. This is a critical step before design, because it shows the shape of the problem we're aiming to solve. We've started mapping job seekers looking for referrals and people learning to cook, and the maps are actually quite good.
The main goal of our first build is learning, and I don't expect it to be a massive success. Still, it's important to be disciplined and declare upfront what a good product looks like. Beyond the app working well, that means:
We expect habit to start out decent and k to start well below 1. Early feedback will tell us whether to focus on making the app more shareable.
UnblockedApple approved our move to a business account (woo!), so we can now build in payments.
David