Vinh P Dinh retweeted
RevenueCat's AI paywall editor is insane, absolutely insane. I pasted the prompt and when I came back, it's all done. Only thing I'm going to have to configure is the products but that's just a few clicks
If you're wading in the swamp of churn prevention, it's already too late. The product sucks and you're just trying to move a few percentage points.
The faster path to a high retention low churn is actually having a real awesome product. Everything else is a small side effect.
Vinh P Dinh retweeted
I would like to take this opportunity of thank @RevenueCat for being an amazing subscription manager for our apps. There is no other service out there worth considering for your projects.
Vinh P Dinh retweeted
Okay this is *crazy*
An agent running entirely on iPad* that can control any app
Vinh P Dinh retweeted
Six weeks ago, I fell down the OpenClaw rabbit hole. One of my experiments was to give it an API key for one of my RevenueCat apps, and I was blown away.
It made things that would take minutes in the dashboard take seconds. With no handholding.
Immediately I started productionizing it, building my first production feature for RevenueCat in 5 years (with some help from some friends). Using codex + claude code, we quickly built up a prototype which is in private beta right now: Rico, our first in-house agent.
revenuecat.com/feature/ai-ag…
It's clear to me now that CRUD software won't be enough anymore. Many interactions with software that were once tedious become magical if you just pour some tokens on it. We will need to reinvent much of what it means to be a SaaS. It will require new thinking, and RevenueCat needs to get there fast.
We now have several agentic features in the works, and I think it's just the beginning. RevenueCat of today is the brain stem, AI and agents are the neocortex we will layer on top to create a truly powerful, thinking machine that will help any developer make more money, autonomously.
As part of that we need help. We're catching up quickly here, learning how to build and deploy agentic systems. But we need to build a team, and I'm looking for the first product engineer to own how intelligence is built into RevenueCat. You'll work directly with me, @elwatto and others to bring the vision to life.
Apply, or send me a DM with the craziest AI system you've built
jobs.ashbyhq.com/revenuecat/…
Vibe coding has unleashed a torrent of new iOS apps in the app store.
After basically zero growth for the past three years, new app releases surged 60% yoy in December (and 24% on a trailing twelve month basis).
Charts of the Week: a16z.news/p/charts-of-the-we…
Vinh P Dinh retweeted
We're less than two weeks away from the 2026 State of Subscription Apps launch
Like we did last year, @drbarnard invited the world's leading voices in b2c apps to join him on @SubClubHQ for 11 mini episodes,
Kicking off with @omooretweets from @a16z:
Vinh P Dinh retweeted
Everyone is talking about the death of consumer apps in the vibe coding era.
But at @a16z, I see B2C AI startups growing and retaining users better than every before.
My takeaways on how consumer founders succeed in the AI era 👇
Vinh P Dinh retweeted
Terminals used to accept shell commands, now it’s natural language.
IDEs used to accept code, now it’s natural language.
Search engines used to accept keywords, now it’s natural language.
Your sites & apps accept clicks, drags, hovers, taps… soon it’ll all be natural language
Vinh P Dinh retweeted
There's a Hampton member who built an app making $4.5m/year.
The app's simple: 1 second videos a day.
I used it when my daughter was born and now we have this amazing 10 minute video of all her days combined.
Simple ideas, done well, that genuinely make lives better.
You can't let the slop and cringe deny you the wonder of AI. This is the most exciting thing we've made computers do since we connected them to the internet. If you spent 2025 being pessimistic or skeptical on AI, why not give the start of 2026 a try with optimism and curiosity?
Vinh P Dinh retweeted
Replying to @antirez
In 2012 we took this wild ride at mobile infra at Facebook when trying to reduce the several-seconds long load time for “Newsfeed”. A few people worked on different approaches. Something we quickly realized was that setting up a connection with TCP and TLS was incredibly slow on mobile networks at the time. The fix was to have just one, keep it alive and multiplex. Shaved a whole second off. But it was still slow. Several people were convince that us sending JSON was the problem, so two different teams started to work on compact binary encoding. After a lot of experimentation what actually worked out best was to send JSON with ordered fields and a compile-time generated parser. Turns out both our iOS and Android app would do something silly like: 1) read all JSON data from server into a buffer, 2) decode that buffer with a generic JSON decoder into lists & dicts, 3) traverse those structures and build the final struct/class tree. Oh and another neat thing we eventually did—when the network connection needed to be setup—was to send an optimistic UDP packet to the server saying “get started fetching data for the following query”; once the real connection was established, TLS handshake completed and user session authenticated, the response was already ready to be sent back.
Vinh P Dinh retweeted
One of my favorite lessons I’ve learnt from working with smart people:
Action produces information. If you’re unsure of what to do, just do anything, even if it’s the wrong thing. This will give you information about what you should actually be doing.
Sounds simple on the surface - the hard part is making it part of your every day working process.
Vinh P Dinh retweeted
Replying to @Jimmyjames_tech
I think a really great folly of modern technology and especially AI is making things that replace the processes we consider incredibly human and precious rather than automating away work we don’t like to do
Vinh P Dinh retweeted
"In the hospital there are kids maimed by airstrikes: missing arms, missing legs, third degree burns. Often there’s not enough pain medication. But the children are not screaming about the pain, they’re screaming: 'I'm hungry! I’m hungry!'"
“When I entered Gaza the Israeli military had a rule: I was only allowed to bring in three kilos of food. As I was weighing out protein bars, trying to get under the limit, I said to my husband: ‘How sinister is this?’ I’m a humanitarian aid worker. Why would there even be a limit on food? I’ve worked in many places with extreme hunger, but what’s so jarring in this context is how cruel it is, how deliberate. I was in Gaza for two months; there’s no way to describe the horror of what’s happening. And I say this as a pediatric ICU doctor who sees children die as part of my work. Among our own staff we have doctors and nurses who are trying to treat patients while hungry, exhausted. They’re living in tents. Some of them have lost fifteen, twenty members of their families. In the hospital there are kids maimed by airstrikes: missing arms, missing legs, third degree burns. Often there’s not enough pain medication. But the children are not screaming about the pain, they’re screaming: ‘I’m hungry! I’m hungry!” I hate to only focus on the kids, because nobody should be starving. But the kids, it just haunts you in a different way. When my two months were finished, I didn’t want to leave. It’s a feeling I haven’t experienced in nearly twenty years of humanitarian assignments. But I felt ashamed. Ashamed to leave my Palestinian colleagues, who were some of the most beautiful and compassionate people that I’ve ever met. I was ashamed as an American, as a human being, that we’ve been unable to stop something that is so clearly a genocide. I remember when our bus pulled out of the buffer zone. Out the window on one side I could see Rafah, which was nothing but rubble. On the other side was lush, green Israel. When we exited the gate, the first thing I saw was a group of Israeli soldiers, sitting at a table, eating lunch. I’ve never felt so nauseous seeing a table full of food.”
-------------------------------------------------------
Aqsa Durrani is a pediatric doctor and board member of Doctors Without Borders USA, with nearly twenty years of experience in humanitarian projects. During our interview Aqsa repeatedly expressed a desire to center the voices of her Palestinian colleagues. To this end I’ve spent the past week collecting stories from the Palestinian staff of Doctors Without Borders in Gaza. I will be sharing these stories over the next several days. I’m so grateful for the time that these people gave me; they were sleepless, hungry, traumatized, and often working 24-hour shifts. Because of the unreliable internet connection their images are sometimes grainy. Their words, however, will be crystal clear.
Vinh P Dinh retweeted
Claude Code has completely changed the way we develop our app, Chorus, so much so that we now consider it one of our employees.
We now put an asterisk on the whiteboard next to any task that Claude will mostly handle. And the asterisks are multiplying.
Here’s what we’ve learned about how to manage Claude.
## Get the easy stuff right
Run /model to see which model you're using. Set it to Opus. It’s more expensive but worth it. I accidentally had it on the default (Sonnet) for weeks. I thought Claude was quiet quitting but I was just using his dumber, cheaper cousin.
Use the Cursor/VSCode extension. You now have a shortcut (CMD+Esc) and it automatically reads the file you’re in and any text you’re highlighting. I’m still using Cursor, but the Claude Code extension has almost completely replaced the AI chat sidebar.
## Start with plan mode
`Shift+Tab Shift+Tab`. This is a recent addition and I’ll use it for any work that doesn’t have a clear and small scope. I have no hard data but planning seems to improve results, and it also helps me think through what I want.
Like any AI, Claude loves to overcomplicate things. It’s a token fountain. Every line of code it writes should give you pain.
I will usually remind it to “keep it as simple as possible.” We don’t need to solve every edge case, we’re a startup, you fool!
## Feed the beast
Paste in links. Paste in images. To paste images you have to use ctrl+v (that’s right, ctrl, not cmd!). I had no idea this existed until we wrote this post and Jackson told me.
Claude can use git and the GitHub command line tool, gh. Ask it to make PRs, resolve merge conflicts, debug using git bisect, etc.
Don’t expect it to know what files to look at. Guide it with some @ s. Claude is good at searching but not amazing, it needs your help.
Imagine you’re sending a human engineer your request. Except you don’t have to be as polite (but maybe you should, who knows).
Tip from @OmidMogasemi: “I’ve found the more I talk to Claude like an engineer I’m pair programming with, the better it performs. This has helped me get over the hump of figuring out what context to give it. You can act like you’re writing a Jira ticket for a junior engineer.”
## Use the magic word(s)
I also will often add “think ultrahard” (thx @simonw) if I want a bit of extra oomph. This is like a secret magical spell to tell Claude to use more tokens. It’s bizarre to me that we live in a world where I am telling you magic secret passphrases to whisper to your AI to make it code better for you, but here we are.
## Watch it cook, or not
Once it’s made a plan, tell it to start implementing. I’m a trusting type so I always Shift+Tab to auto-accept edits.
Don’t be afraid to esc and do some more explaining if you think it’s going down a bad path.
Something I still haven’t figured out: what do I do while Claude is working? It’s impossible to get into a flow state with these vibe coding tool like I do when I code with my raw brain. Here’s one solution, let me know if you have any better ideas: teapawt.net/charliebholtz/status/1…
🚨 The Most Dangerous Trap 🚨
If you are having trouble—let’s say you’ve asked Claude the same things 3–4 times with different strategies and you’re getting nowhere—pull the eject button and give up. You are entering what I call the “rabbit hole problem.”
Vibecoding is powerful but the absolute worst version of it is lazily throwing stuff at the wall, it not working, and then spamming the chat. It's really hard to fight this, and I usually catch myself when it’s too late, when I’m tired and I don’t want to put in the effort of actually thinking through the problem.
Something that helps is to think of all the work as helping YOU think about the problem. Don't view code the AI wrote as having the same weight as code you wrote. You can throw it all away and it doesn’t matter.
One useful strategy here is to start over with a fresh context (see “Ask Claude to review” below).
## Review the code
The hardest part is knowing whether Claude’s work was any good.
With Chorus, Claude can’t interact with our app, so I ask it to write a testing plan I can manually check off. Here’s a testing plan Claude wrote in a PR description (as you can see, I skipped the hard parts):
You can also spin up a second Claude instance and ask it to review the work. Each Claude tends to be very attached to its own work, and will find it much easier to criticize other Claudes. (Hey, that reminds me of someone!) Often I’ll ask some other AIs in Chorus if I feel like I’m going down a bad path.
How do you spin up a new Claude instance? The easy way is /clear, but that will also irrecoverably wipe out your chat context, which you might want to return to. I usually just open a new pane in my terminal. Yes, this eventually becomes a huge pain.
On harder tasks, I’ve found myself repeating, at least 2-3 times: Can you double check this is as simple as it can be?
As a last step, and I know this sounds insane, but hear me out—read the code yourself. Be suspicious. Claude loves to cut corners. It’s constantly using ref to get out of changing the React state model, or using typecasts so it can avoid figuring out the right types.
## Keep teaching
Whenever Claude messes up, put # in front of the correction. The instruction gets saved to Claude’s memory (stored in CLAUDE md), and Claude will follow it in future sessions.
If possible you should check CLAUDE md into source control.
## When not to use Claude
I don’t use it for UI work. There’s a distinctive LLM design language that I can’t quite put my finger on but just looks shitty. I see it in apps created with Lovable, Bolt, etc.
Human designers (like @julianfkelly ) are miles better.
I also wouldn’t use Claude to write code I’m going to build on a lot later on, where each tiny design decision I make now will become a massive binding constraint down the road. It’s still helpful for thinking through how to implement these things, though.
## What does this all mean?
Things are changing really fast, and we’re still figuring out how to work with our newfound sand intelligences.
I’ve been surprised how much I’ve started to trust Claude. The game changer here is that it can do full scoped units of work. Even for things it can't finish, it gets the ball rolling, which is often the hardest part.
Congrats to you, Claude, employee of the month!





























