Mike Khristo is CEO and co-founder of Layers.
Your CI pipeline doesn't wait for you. A commit triggers a build, the build runs tests, the tests gate the deploy, the deploy produces telemetry, and that telemetry shapes your next commit. Nobody runs those five stages as separate manual jobs with a human carrying artifacts between them anymore.
Now look at how you run growth. Keyword research in one tab, content in another, scheduling in a third, ad platforms in a fourth, analytics in a fifth. You are the connective tissue, usually at 11pm, pasting context between tools that don't talk to each other.
Here's the thing: growth compounds the same way your pipeline does, through loops, not funnels. And the gap between apps that compound and apps that plateau is usually just how many manual handoffs sit inside that loop.
In July, Liam Du wrote about taking Wellspoken from 400 users to hundreds of thousands of downloads. His first lesson: growth is a portfolio, no single channel got him there. True. But read his story again and you'll notice something else: the components are wired together. Retention lifts his App Store ranking, the ranking brings installs, and those installs produce the signals that lift the ranking again. His UGC operation finds a format that converts, converted users leave reviews, and the reviews make the next batch of content convert better.
Every output feeds an input. That's a loop, and he built a good one. Most people run the same components as a checklist instead.
Funnels end. A loop feeds itself.
A funnel is a sequence with an exit at the bottom. Traffic arrives, a fraction converts, and the only way to get more out is to put more in at the top. Every gain is linear, and every gain is bought.
A loop routes its own output back into its own input. Users generate something (retention data, reviews, content, referrals), and that something makes the next cycle cheaper than the last one. The compounding is structural, not something you're buying with ad spend.
The three loops most apps can actually run
The store loop. Installs create behavioral signals that help stores figure out which results are useful, and ratings, reviews, and app quality affect discovery too. Better visibility produces more installs. The interesting recent shift is semantic relevance: in February 2026, Apple published research on an LLM-assisted App Store ranker that balances behavioral signals with how well an app actually matches a search. The biggest gains showed up on tail queries, where there's less historical behavior to learn from. For a new app, that's an argument for targeting specific, semantically clear searches instead of leaning only on broad category terms. Cycle time: weeks.
The content loop. You build something, capture it, post it, see what lands, make more of what landed. In a dataset of 23 million short-form videos, a follow-up on the same topic at the same length after a hit earned roughly 36% more views than switching subjects. The window is generous at first (two hours later and four days later perform about the same), then it closes after about a week. Cycle time: days.
The proof loop. Usage generates reviews and user content, that social proof raises conversion, and higher conversion brings more usage. Liam's point about review prompts is the right one: the prompt just harvests sentiment about a product that already earned it. This loop only runs if the product deserves it. Cycle time: continuous.
Notice the pattern. The content loop has the shortest natural cycle time of the three, and for most solo developers it's also the slowest in practice, because it's the most manual.
Loops fail in two places
Latency. A loop compounds at the rate it completes cycles. If it takes two weeks to figure out what performed, the context that made it perform has already moved on. That's why the sequel window matters: the advantage is real and it expires. A winning post is evidence about a moment. Platforms tell you what worked. None of them tell you why.
Handoffs. Every point where a human copies context from one tool into another is a place the loop stalls. Liam solved this with dozens of creators and a campaign manager, which works, and is completely out of reach for most people reading this.
Why we built Layers
The parallel to Expo is hard to miss here.
Ten years ago, shipping cross-platform meant maintaining a toolchain: the right Xcode on the right machine, signing, submission, a separate "everything" for Android. Most of that work was connective tissue, and the connective tissue was a person. EAS collapsed it. A solo developer can now run an app with hundreds of thousands of users without ever opening Xcode, because the steps between commit and store stopped needing someone in the middle.
The growth stack sits roughly where the build stack used to sit. Same shape of problem, same disconnected steps, same person stuck in the middle doing the gluing. We started Layers to close those handoffs, built on one belief: generative systems are only as good as the structured context they get before they generate. Brand guidelines and a URL are thin context. Your codebase, your store listing, and your usage data are thick context, and all of it is already sitting there unused.
That's the product argument, and I'll leave it there. The part that's useful no matter what you use is this: optimize for cycle time and count your handoffs.
What to do on Monday
Draw your loop. Four or five nodes, arrows showing what feeds what. Most people discover they actually have a funnel with a hopeful arrow drawn at the end.
Time each leg. How long from shipping a feature to content about it going live? From a post landing to a follow-up? From a retention gain to seeing it move your ranking? Whichever leg is slowest sets your overall compounding rate.
Remove one human handoff. Pick the leg with the worst ratio of time spent to judgment required. It's almost always a copy-paste step, and it's usually the one choking your content loop specifically.
Feed it something you're currently throwing away. Every app produces raw material continuously, and most of it gets used once and deleted. Your changelog is content. Your support inbox holds the exact words people use to describe their problem, which is where your store copy and keywords should come from in the first place. Generated output can carry the volume, but the raw material has to come from you, and it's most useful the week it shows up.
The loop is already there. The only question is how fast it turns.
This post is based on content from the Expo blog. Follow @expo for more React Native content.
Top comments (2)
The store loop is the one I wish more early founders planned for before launch. With most clients I've found ratings and retention get treated as a post launch problem, when the first build is where you decide when to ask for a review and what brings people back. Wiring that in early is cheap compared to retrofitting it later.
Đúng trọng điểm. Pipeline CI/CD bản chất là feedback loop — chạy, đo, điều chỉnh, lặp lại. Mỗi commit là một lần validate hypothesis. Nhưng growth stack (analytics, feature flags, experimentation, onboarding flows...) lại thường bị đóng khung thành "setup xong là xong", quên rằng nó cũng cần iteration velocity ngang ngửa với code.
Thực tế thấy nhiều team: deploy 10 lần/ngày, nhưng A/B test một feature mất 2 tuần vì feature flag system cồng kềnh, hoặc event tracking lệch vì schema không versioned. Growth infrastructure đáng lẽ phải được treat như first-class citizen trong pipeline: testable, rollbackable, observable.
Một pattern hay áp dụng: gắn growth metrics vào PR checks (ví dụ: "PR này làm thay đổi funnel step X, cần có experiment plan"). Buộc dev + PM đồng bộ ngay tại commit — tránh việc "ship xong mới lo measure" (site: labagent .tech)