... 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 ... ... have anyway. The cheap failure here is a rejected submission on release day. The expensive one is shipping a small "share" button in a point release and never revisiting a declaration you made a year ago. 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 ... ... probably a floor for voice, not a ceiling. curious if the paper (or anyone here) has looked at whether audio/TTS-mediated delivery changes the compliance rate at all, or if that's just unstudied territory right now 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 Mona

... Comment from Johanna John(@johanna_john1): @monatruong_murror  Exactly. It is the kind of task that can easily get missed because nobody clearly owns it. Starting early seems much safer than waiting until it becomes urgent. Comment from Mona Truong(@monatruong_murror): @johanna_john1  If it helps: the cheapest way to give it an owner is to make it a purchasing task rather than a compliance one. It's a number you request from Dun & Bradstreet ... ... planned for. Comment from Joseph Collins(@joseph_collins2): i would be interested in hearing how many developers actually know where their signing key is today. that might be the most useful test of this whole change. 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

... categories on purpose, and write down why. Not because Cloudflare's defaults are wrong, mostly they're reasonable, but because a default you never chose becomes a strategy by attrition. This one has a date on it. Comment from Mona Truong(@monatruong_murror): @serdarships  Varying the client is the axis I'd have missed entirely, and it's the more dangerous one. A path that behaves differently by header isn't a bug you can find by walking ... ... Enterprise, you're back to the rolling dashboard window, which is a glance rather than a record. Which leaves the gap-diff you described as still the right instinct, just with worse tooling than it deserves. Comment from Mona

... that the metric that used to mean "it's working" now means two things at once, and you need to be able to read both. Engagement is still the signal. It's just no longer free. Comment from Mona Truong(@monatruong_murror): @siarheihamanovich  The refund path is the part I hadn't considered, and it's the best argument for credits I've heard. It forces you to know what one call costs. Flat-rate lets you avoid that ... ... refill event, nothing to read. Best I have there is the balance at the last session: if someone's final visit ended with credits still in the account, they didn't hit a wall, they just left. 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 ... ... making the caller declare itself explicitly rather than trying to infer it, because guessing wrong in either direction costs more than the two-surface work does. curious if you've found a cleaner signal than just asking. 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 ...

... year it's noise. They'll be the ones who built a small, honest, embarrassingly manual way to see what their thing actually does to real people and looked at it often enough to catch it drifting. Comment from Mona Truong(@monatruong_murror): @getosmo  "Tagged by failure mode rather than benchmark name" is the line I wish I'd written. That's the whole thing. Once the cases are organized by how it breaks, the set stops being ...

... 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

... weight by turn 15. feels like the actual skill isn't deciding what to leave out once, it's re-deciding it continuously, which is a much harder engineering problem than just writing a tighter system prompt. Comment from Mona Truong(@monatruong_murror): @omri_ben_shoham1   Yes that's the part I underplayed in the post. Curating once is a prompt; re-deciding every turn is a system. What's helped us is treating context assembly as a step ...

... good one. you still need a human (ideally not the builder) to break the tie. feels like it narrows the blind-reading problem down to a much smaller, cheaper set of cases rather than solving it outright Comment from Mona Truong(@monatruong_murror): @omri_ben_shoham1  Exactly and that "ideally not the builder" part is the bit I keep relearning the hard way. On subjective output the builder is close to the worst possible judge, because I unconsciously grade ...

... 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 ... ... abstract: the AI coding tools that spread fastest did it through something people could point at a generated PR, a public run not an invite-a-friend prompt bolted on after launch. Probably the cleanest version of "output vs

... 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

... answer. Have you found anything that actually works for tracking this over time, even roughly? That feels like the missing half everyone can see the problem now, but almost nobody can see if they're fixing it. Comment from Mona Truong(@monatruong_murror): @saied_alimoradi  You've put your finger on the actual missing half, and I'll be honest: I don't have a clean answer, because there isn't a Search Console for this ... ... line, and the drift is usually visible to the naked eye before any metric would catch it. Honest state of the art is "measure it manually and consistently," which is unsatisfying, but pretending otherwise would be worse. 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 ... ... about: when your user closes the app, are they better off, or just less alone for the next four minutes? Your roadmap already knows the answer. The question is whether your metrics will let you admit it. Comment from Mona