... product sense before it was a legal question, and it's nice when the two agree. Which of your products would you have put under the emotion rule, and would you have gotten Article 50(1) right? Comment from Mona Truong(@monatruong_murror): @galdayan  Good catch, and my read did stop at text. I only worked through it for a typed-journaling product, so I haven't done the analysis for voice and wouldn't want to hand ...

... reading from acting point is especially important. Giving agents broad access by default can turn a simple prompt-injection issue into a real-world action. Least privilege + human approval for sensitive actions feels like the right approach. Comment from Mona Truong(@monatruong_murror): @galdayan  Thanks Gal, that's a useful way to put it: the guardrail that held up was on actions, and the read side is the part nobody audits because nothing visibly goes wrong. One cheap thing ... ... what it could reach. If it only ever touches the last few weeks of mail, you can scope it to that and the "years of email" exposure goes away without changing what it does for you. Comment from Mona

... evolved. It s the kind of IDE-native documentation layer I always wished existed. I m opening early access for engineers who want to try it and shape the direction. If you re curious, here s the waitlist: codetrackerai.com Mona Hidalgo Founder & Software Engineer Mix It Hub, LLC I d love to hear: What s the biggest code understanding pain you deal with in your IDE? Your feedback will directly influence what we build next ...

... that the age rating questionnaire now includes questions about social media capabilities, and that "beginning in September 2026, responses will be required when submitting new apps or updates to the App Store, or when submitting apps for notarization for alternative distribution." September ends tomorrow, so if you have a build in flight, this is the week you meet it. Apple's definition is narrow: the ability to redistribute, amplify, or interact with user-generated content through a social feed ... ... point release and never revisiting a declaration you made a year ago. Comment from Manuel Lorenzo Bouzada(@bouzadamanuel0934): I hadn't really thought of the age signal as useful product information too, not just an Apple requirement. Comment from Mona

... absence would stop the product doing one of its functions. If your app is a thin client over your API, that API is not a separate service you can wave at. It's part of the product. This product-versus-service line is the genuinely contested bit, and I'm reading the Commission's guidance and a pile of law firm notes rather than a court ruling. I'm a founder, not a lawyer. If you're near the boundary ... ... ENISA's SRP FAQ. It's the operational one, it's updated regularly, and the last time it changed was 17 September, five days ago. The coverage is not going to tell you about the counter. Comment from Mona

... nobody covered, which is worse, because it changes a line of code a lot of us shipped this year without thinking about it. If your product has a "paste a URL" box, a link unfurler, an enrichment step, a competitor-monitoring job, or anything that fetches a page and hands it to a model, this is about you. What was actually measured. The paper is "Indirect Prompt Injection in the Wild" by Khodayari, Zhang, Acharya and Pellegrino, out of CISPA ... ... knew. One last thing. 65% of the pages in that dataset already contained their prompt 12 months before the analysis. This is not a new risk arriving. It's an old one you've been ingesting. Comment from Mona

... right and is more useful than either, and the revised version went up this month, so it's worth twenty minutes before you write your Q4 plan. It's NBER working paper 35275, Demirer, Musolff and Yang - "Writing Code vs. Shipping Code." More than 500,000 GitHub developers, matched against their actual AI usage telemetry rather than a survey, in a matched event study design. The headline numbers are large and I have no interest in arguing with them. Cumulative ... ... most want replicated by someone with no Microsoft relationship at all. And "releases" is a crude proxy for value - a team shipping fewer, larger releases isn't underperforming, it just looks that way in this data. Comment from Mona

... Apple's own support pages. Apple In-App Purchase: 26%, or 15% if you're in the Small Business Program, the Mini Apps or Video Partner Programs, or on an auto-renewable subscription after the subscriber's first year. Alternative payment processing inside your app: 20%, or 10% for those same groups. Out-of-app offers with an actionable link: a 15% store services commission, or 10% for those groups, on anything bought within 7 days of the tap. Apps ... ... distributed outside the App Store entirely - an alternative

... Three numbers from it get quoted. Users who saw an AI summary clicked a traditional result in 8% of visits; users who didn't, 15%. Users ended their browsing session 26% of the time with an AI summary present versus 16% without. And the one that should matter most to anyone buying GEO: users clicked a link inside the AI summary itself in 1% of visits. One per cent. That is the click value of the thing the entire optimisation ... ... more often. Just 8% of one- or two-word searches produced one. For searches of ten words or more, 53%. For searches starting with a question word - who, what, when, why - 60%. Sit with that next to the 8%-versus

... line appears in both: starting September 2026, you're required to indicate whether your app or game includes social media capabilities in order to submit new versions or updates to the App Store, or for notarization for distribution on alternative marketplaces. It's September. It's live. I read both pages this week rather than the coverage, partly because Murror is the kind of app where the answer isn't obvious, and partly because the second-order effects aren ... ... allowances are in actual minutes. And "visibly spreads content to many users" has no threshold attached to it that I can find. If your feature is genuinely borderline, the person to ask is App Review, not me. Comment from Mona

... times. I'm a founder, not a lawyer, and none of this is legal advice - but the arithmetic of which paragraph applies to you is something you can do yourself in twenty minutes, and it's cheaper than the alternative. Comment from Siarhei Hamanovich(@siarheihamanovich): @monatruong_murror  Every flashcard generation writes a record because that's how the billing works, so which model produced what, for which account, at what time is already in the database. Keeping the fields ... ... haven't signed the Code of Practice. What I did change is when the decision happens. Marking is an export-time decision rather than a UI one, and every file already out there predates whatever you decide Comment from Mona

... could have. And I still don't have a clean answer on the verification-method question, because the honest version is that I don't yet know what I'd do differently with a government-ID-checked 16 versus a self-declared one. I'd rather say that than write a paragraph pretending I've resolved it. The thing I am confident about is narrower. The signal is sparse for a long while yet. Texas only covers accounts created after ... ... support-load event you'd much rather see coming than hear about. None of that is hard. It's just that none of it happens by default, and the default here has a penalty clause attached. Comment from Mona

... built around that, so the failing cases are the ones nobody has a reason to visit. I have no method for generating them rather than stumbling into them. If you have one I would take it. Comment from Mona Truong(@monatruong_murror): @omri_ben_shoham1  That's the part I under-weighted, and it's the better version of my point. A blocked crawler leaves a mark somewhere eventually, a coverage drop, a grey row, something ... ... think of is watching 403s by user agent on your own pricing and docs pages and treating any non-zero number as a decision you should have made on purpose. Nobody does it, because nothing fires. Comment from Mona

... real person uses is enormous, and that gap is where products in spaces like mine quietly disappear. I don't have this solved. I've just stopped assuming the name is the thing that gets found. Comment from Mona Truong(@monatruong_murror): @jernej_jan_kocica  The permanence is the part I didn't know, and it changes the order of operations. If a declined category can never be requested again, the submission is the whole decision so the work ... ... content/entity gap; if Murror is cited but sends no visits, it is visibility without acquisition. That separation should keep a tiny referral channel from being mistaken for proof that the product is absent from the buying conversation. Comment from Mona

... destination? If the value is a result someone wants and doesn't care how they got an action then being agent-callable is close to free distribution and you should be looking hard at it before your competitor does. If the value is the experience of a person actually being there a destination then racing to become a tool call is optimizing for a future where your product's whole reason for existing has been abstracted away. Worse ... ... sequence that adds up to something consequential without any single step qualifying is a totally different, much harder problem, and it's usually the one people forget to build for after they ship the bright-line version Comment from Mona

... small it moved onto exactly one desk. Comment from Ill Robyn(@ill_robyn): The idea of treating review as a budget really stands out. Asimple rule like that could stop AI generated work from piling up unnoticed. Comment from Mona Truong(@monatruong_murror): @ill_robyn Thanks and the reason it ended up as a budget rather than a rule is that I failed at every stricter version first. "Always review AI output" has no partial credit: the first week ...

... ones who copied the pricing page that was winning last quarter. They'll be the ones who priced the thing they actually do, especially when the thing they do can't be reduced to a number. Comment from Mona Truong(@monatruong_murror): @joseph_walker2   Thanks for reading it that closely. That's exactly the test I now run before shipping any plan: would this number go up if my users were having a worse week? If the answer ...

... Mona, a marketer turned founder from Germany. I'm building Xolora, a marketing analytics tool dedicated to solopreneurs and small business owners. I noticed that 80% of that niche is overwhelmed with their marketing and just guessing. When it comes to ads, this means that they're wasting money (around $10,000/year). And the sad truth is that there is no tool out there, that helps them. All the other marketing tools are made for marketers or big teams ... ... underserved niche. Xolora's goal is to simplify ad analytics, give back time, money and ultimately confidence. It just launched in beta and I hope that it will be valuable for its users. What is your niche? Comment from Mona

... judgment, your ability to stay steady when the feedback is loud and instant and mostly noise. In 2026, taking care of the builder is not self-help fluff. It's the actual bottleneck. Treat it like one. Comment from Mona Truong(@monatruong_murror): @omri_ben_shoham1   The recovery is exactly where mine used to fall apart too, and the fix was killing the streak entirely. There's nothing to break. It's not a chain I'm protecting, just ... ... whole thing collapsed. Making each day independent removed that. The only recovery rule I keep: never judge two days' numbers at once to catch up that's just the mid-build spiral wearing a productivity costume. Comment from Mona

... this: if building is no longer the moat, then the moat is available to anyone willing to do the unglamorous work. Knowing your person. Owning a relationship instead of renting attention. Being early to a workflow before a competitor gets embedded in it. None of that requires funding or a team. It requires you to stop hiding in the part of the work that feels productive and go do the part that actually decides whether the thing lives. Ship ... ... later, after I had a few users, answering the exact questions they asked me. Fewer posts, aimed at stuff people were already searching. Thanks for writing this, the after-launch part is the part nobody posts about. Comment from Mona

... transcripts starts accurate and then decays, not because the model changed but because your users did. Which means it has to be refreshed from live traffic on a schedule, or in a year you have rebuilt the exact lab-versus-real gap you made it to avoid. Comment from Mona

... sentence an AI says about you when you're not in the room. You can't write that sentence. You can only be the kind of product it's easy to say something true and good about. Comment from Mona Truong(@monatruong_murror): @raffay_sajjad  That "a little scared of what it says back" is exactly the right feeling to have before running it. Mine came back describing a version of the product we'd moved past a year ... ... sentence to an actual friend. If they get it, the models have a shot. If your friend squints, that's the real bug, and no prompt fixes it. Would genuinely love to hear what comes back tonight. Comment from Mona

... inside your app if they can only feel understood while they're talking to your model you haven't solved loneliness. You've made it more comfortable to stay lonely. You've built a very sophisticated waiting room. The alternative is to design for the exit. Concretely, that means three things. Point users back at real people, not deeper into the app. The most valuable thing an emotional AI can do isn't be a better listener than your friends ... ... thats a feature not a bug. teams that build a way to capture that external signal, even at low volume, get to measure what the regulator actually cares about. everyone else is defending against DAU accusations forever. Comment from Mona

... builders land on this. When you imagine your product working perfectly, does usage go up forever, or does someone get what they needed and walk away? And which one were you actually optimizing for? Comment from Asad M.(@asadmalik901): Mona, the test is sharp, but I think it hides a third case, and it is the one most tools actually live in. Some products are not trying to finish a job or to keep you hooked. They are a place ... ... whether the work still gets done during it. Comment from Nika(@busmark_w_nika): imo, the whole thing with AI agents is becoming oversaturated the same way as it was with AI in 2024 Comment from Stacy Wycoff(@stacywycof83995): Mona

... metrics say yes. Anyone else held the line on a feature like this? Curious how you explain the "no" to users who genuinely want it. Comment from Asad M.(@asadmalik901): @monatruong_murror   This made my day, thank you Mona. The fact that you were already testing the gentle prompt before we talked tells me the instinct was there, you just needed the words for it. One thing I would watch as you build it: the risk with a lighter ... ... door is that it quietly becomes the default one, so the real win is if it stays the exception and hands people back to the writing quickly. Rooting for you and the team on this. Comment from Mona