Stop releasing your app to change its content.
Today, every content change needs developer work, a new build, a store review, and a wait. And the next change starts the same loop again. ContentFlow ends the loop: one engineering integration up front, then your team publishes content changes without a new app build and without a new app store submission.
All live at once. Instantly, no release.
Any new campaign, any new instance of any component: several at the same time, live the moment you publish.
Map out and customize anything in your app.
Home screen
2 addedAlso available here: banners, cards, whole sections, full screens.
You add it in the dashboard, the app shows it. No build, no store review, no waiting. Remove it the same way.
Change colors, text, and images yourself.
No presets. Pick a new accent color, retype the promo line, swap the header art. The live app never moves while you work: every edit stages as a draft, and one publish lands them all together on every phone.
Home screen · v14 · published to every deviceHome screen
PublishedEvery component is managed content, not just messages.
Most tools stop at in-app messaging: a bubble that floats over the app for a moment, then is gone. ContentFlow manages the app itself. Every block on every screen is hosted, versioned, targeted content you can update at any time.
Header, hero, cards, promo, nav. Every surface is a block you own: hosted, versioned, targeted, updated any time.
One temporary overlay. The app behind it is frozen until the next release.
What this changes for the business.
When content ships without a release, seasonal moments stop being engineering projects.
Seasonal campaigns reach every device the moment marketing hits publish. Not weeks later.
No build, no store review, no rollout window for a content change. A change to your app's own code still goes through Apple and Google review. Rollback is one click away.
Campaign teams change the app without an engineering ticket or a sprint slot.
Impressions, taps, and conversions per block, per version, per segment.
Eid, National Day, Ramadan, back to school. Every season ships the day you decide.
Test two versions on real users.
One experiment pushes the same offer in two different creatives to two user groups. ContentFlow measures both, and you publish the winner to everyone.
Version B wins.
Publish it to 100% of users in one click. The losing version disappears instantly, and the next experiment starts from the dashboard, not from a release.
See Dynamic Blocks in your own app.
This is the real dashboard. In a 30-minute walkthrough we map your screens to blocks and make your first no-release change together.
Production integration today uses the REST API. Native SDKs for React Native, iOS, Android and Web are in preview and are not generally available. The @contentflow/cli package is not published yet.
Publishing content through ContentFlow does not require a new build or a new store submission. Any change to your app's own code still goes through Apple and Google review, and remotely delivered content has to stay inside the purpose your app already declares and the store policies that apply to it.
Book a demo Or press Escape to return to the main deck.