Apple is reportedly pushing back on AI vibe coding apps like @Replit and @Vibecode App, tools that let users create apps just by typing prompts.

The issue isn t a new rule. Apple is enforcing an old one:

• Apps must be self-contained

• They can t download or run new code that changes functionality after review

We're an AI-native startup shipping fast with augmented coding, but the debt it creates is different from anything I've seen before.

I remember in my old team we put aside around ~20% of engineering time to pay down debt that accumulated during feature releases.

My terminal coding agent had hit its weekly limit and I had a small bug sitting in my queue, the kind of thing that would normally take one prompt and thirty seconds, so I figured I'd just fix it myself while I waited.

Took me almost the full thirty minutes. Not because the bug was hard, it genuinely wasn't, but because I kept reaching for a keyboard shortcut that wasn't there and realized I'd forgotten the actual syntax for something I used to type without thinking. Had to look up documentation I would've known cold two years ago.

Got it fixed right as the coding agent's limit was reset and honestly felt a little relieved, like I'd passed some test I didn't know I was taking. But it also left me wondering how much of that muscle is still in there versus how much I've quietly outsourced without noticing, since it's not like there was ever a single moment where I decided to stop practicing it.

Has anyone else tried this on purpose, going a day without the assistant just to check? Would you actually want to know the answer, or is it better not to look too closely at how much you've forgotten?

disclaimer: I'm not an engineer. i do growth and marketing.

when people talk about vibe coding they usually mean shipping a product. an app, a saas, a tool with real users. that's the version that gets posted. but it's not where things actually changed for me.

Hey, I was wondering how many of you are coding from the phone - it's easier to do it with AI coding agents now, so I'm wondering how often developers are doing it.

Personally, I do some coding tasks daily from my phone and I'm curious how others are doing it?

Non-technical founder here, built my whole product with Claude Code. Everyone in this forum keeps saying the same thing UI and analytics get the "looks fine, ship it" treatment, but billing and auth get the paranoid line-by-line review. I've lived that.

Here's the twist though: my product IS the billing edge case. It's a tool that recovers failed subscription payments, so the entire thing lives in the messy world of declined cards expired cards, insufficient funds, bank 3-D Secure/SCA challenges that all look similar in the data but need completely different handling. Vibe-coding something where a wrong branch means someone gets emailed "your card was declined" when it actually went through was genuinely terrifying. I couldn't just trust the vibes.

Let me know if this sounds familiar:

Me: Implement issue ABC and satisfy every acceptance criterion in the spec.

Hey PH mates!

I ve been tracking my own workflow lately while chatting around with ChatGPT and Gemini, and I noticed a painful pattern: I had the whole picture in my mind, but I constantly forget some edge cases or tiny technical constraints on my first try.

I hit send, wait 30 seconds, realise the AI guessed wrong, tweak it, and retry. It s an absolute token-waster and a massive productivity killer.

I'm trying to prototype a lightweight extension to intercept these "blind spots" in real-time right inside the input box before hitting send. But I'm curious about how you lot deal with this:

OP-ED?
Recently I've been finding myself actually buying and downloading apps more than before. The common thread? They're all silly things that almost do nothing.
I say almost because what they do offer is a bit of joy during my work day. Some of the recent apps I've purchased or downloaded are @Klack, Googly Eyes, @Docko, @Ball,@TabTab, and @NotchNook.
Some of these do have productivity or quality of life improvements (looking at the last two) but others are simply about making the computer fun again.
For example @Klack has genuinely made me more focused when I type and I've been able to zone in on work. It's like each clickity-clack is driving me closer to where I want to go and idk, the feedback just feels GOOD. The audio is also really nice, not sure how I can explain it, but feels very high-def for something that is mimicking a tactical feeling.
All these apps remind me of a time where shareware and P2P ( @Limewire ) was more popular. Where you might be okay buying a CD or floppy and installing something fun on your computer, then telling (sharing) your buddy about it. And with the rise of vibe coding, I think we're going to see vibeware become a thing. Where users will create something fun, quickly, using AI tools like @Cursor, @Replit, or @bolt.new/@Lovable and then put it at a super low cost or have a free-trial (shareware).
Those that don't want to pay, will create their own iteration of it and choose their own distribution method (P2P) but it won't eat at the original.
It's my genuine feeling that the internet is about to become fun again (it's already started) and I'm curious if I'm the only one feeling this way and/or embracing it?
What do you think? Is the era of vibeware a good thing? And if not why should we refute it?
This piece was written with FKJ - Just Piano in the background.

not talking about the obvious stuff like "don't rm -rf prod", more the gray area tasks where the agent is probably right but you still want eyes on it before it goes out.

for me it's anything that changes a pricing table or a billing calculation. I'll let an agent refactor half my codebase overnight, but the second a PR touches how much someone gets charged, I read every line myself even if the diff is three characters. one off-by-one there and it's not a bug report, it's a support ticket and a refund.