I ve noticed Shopify s new website relies heavily on GSAP for many of its animations and interactions, and it got me wondering how widely it s actually used. For Shopify developers, agencies, and merchants: * Do you use GSAP in production?
* Are merchants requesting Apple-style scrolling and motion effects?
* Is GSAP becoming a standard for premium Shopify stores, or is it still fairly niche?
* If you don t use it, what s stopping you complexity, performance, maintenance, or something else?
As AI development shifts rapidly from simple stateless chat completions to fully autonomous agentic workflows ( @Claude Code , @Aider , @Langchain , @CrewAI AMP - Agent Management Platform ), we are encountering a fundamental challenge in software architecture: The Agent Readiness Gap.
Unlike traditional deterministic software where API calls are predictable and bounded autonomous agents operate in multi-turn OODA loops (Observe, Orient, Decide, Act).
We expected users to ask for more features. Instead, they kept asking for fewer steps to complete the same task. That changed the way we think about product development. Adding functionality isn t always progress. Sometimes removing friction creates much more value. Has customer feedback ever completely changed the direction of your product?
I've been thinking about this more and more lately. Are we all still building in public?
In this era where AI is giving anyone the ability to replicate your company quite quickly, it seems like building in public probably brings more problems than benefits, especially early on. I've seen quite a few people complain about this, even those with large accounts that rely on building in public for distribution. Would love to get your thoughts. It's honestly the first time I'm holding a lot more of my cards closer to my chest.
Coming from an engineering and agency background, our default mindset was always to write clean, fully modular, and perfectly scalable code before pushing anything to production.
However, building our own Micro-SaaS products quickly shattered that mindset.
We learned the hard way that spending weeks over-architecting a feature that users might not even want is the fastest way to waste momentum. Shifting to "shipping fast and listening to user feedback" forced us to make uncomfortable trade-offs between technical debt and speed.
I ve been thinking a lot lately about how creators especially podcasters, YouTubers, and indie writers often get overlooked by mainstream tools that try to serve everyone at once.
Curious to hear what small, purpose-built products people here are building that genuinely serve a creator niche.
Most complaints I get are not new. They are old, quiet, and only turn into a complaint once someone finally runs out of patience. By the time I hear it, the person has usually been annoyed for weeks and just never said anything, or said something small that I did not register as a warning. Curious whether that pattern is just me, or whether the actual complaint almost always arrives later than the moment the person first felt it.
Every one of my businesses has one of these somewhere right now, a message I read, decided was not urgent, and then lost inside everything else that felt more urgent in the moment. By the time I remember it, I cannot always tell if it still needs a fast reply or if the moment already passed. Curious how everyone else catches these before they turn into an apology text. Is it a system, a habit, or mostly luck.
