I ve been thinking about a problem that seems to become more difficult as products grow: adding features can make a product more capable while also making the experience harder to understand.
A product might start with one clear workflow, then gradually add dashboards, integrations, settings, automation, notifications, and other features. Eventually, the challenge isn't necessarily what should we build next? but how do we keep the main experience simple?
My instinct is to separate the core workflow from everything else and make secondary features progressively discoverable rather than putting everything in front of the user at once. But I m not sure that works equally well for every type of product.
For people who have built or redesigned products as they grew:
I ve been thinking about a problem that I m sure many technical founders and Makers here can relate to.
I m a Senior Software Engineer with 5+ years of experience, and I ve built 300+ Android, iOS, and web applications across areas like education, healthcare, productivity, AI tools, and business software.
Over time, I ve realized that building the product is often easier than getting it in front of the right customers.
As a technical person, I m comfortable with product development, architecture, UI/UX, backend systems, AI integrations, deployment, and turning ideas into working products.
Is it normal to get contacted by someone selling upvotes @ $2/vote? From the actual email: "$2/upvote. Growth: $499 250 upvotes, 50 comments, 25 reviews, 10 followers (20% off). " Needless to say, I will never do this but will happily name & shame the sender.
As of August 2, 2026, the EU AI Act's high risk provisions are enforceable, meaning agentic AI systems now legally require human oversight and conformity assessments. Fines for non compliance can hit 15 million euros or 3% of global revenue.
What's interesting is that "human oversight" isn't clearly defined in most implementations I've seen. Does it mean a human reviews every action before it happens? Only high risk actions? A log someone can audit after the fact?
I've seen a few teams building agent products wrestle with this exact call for every action type, not as a compliance checkbox, but because it genuinely changes how much you can trust the thing day to day.
had one this week. a framework update changed how apps launch, and one function kept working exactly as before except the data it hands you is now empty. no crash, no warning, nothing deprecated. deep links just silently stopped opening.
took me a while to find because nothing failed. it all looked like success.
Well I do, and after working on one the better half of last year I have started the preparation phase. What I have done so far is collect all my conversations from last year - which were many, add them to NotebookLM and start asking questions. That was very fruitful at frist, but after a while I had the feeling I was just hitting the surface. Surely I extracted maybe 30 pages of data or more, but since I worked like a real architect during those conversation there was a lot of detail included. Eventually I ended up asking notebook to give me the name of the files that included everything about how to build the AI and let ChatGPT read them one by one to extract the details. That made all the difference. Without this we would have built a galvanised version of the old transformer system. That is not what it is going to become.
So what are your thoughts about a private local LM? What would you prefer? an assistant, a friend or 'something else'?
I work on Shopify apps, and this is something I genuinely can't resolve.
Group buying where shoppers team up so everyone unlocks a lower price is enormous in Asian ecommerce. Pinduoduo built a top-tier company on the mechanic. In the West it's essentially absent. Groupon isn't a counterexample: that was a marketplace selling daily deals, not a shopper recruiting other shoppers into a shared purchase.