The next-gen CMS for mobile apps.

Integrate the Unflow SDK with just a few lines of code so your whole team can ship fully native screens instantly.

Getting started

Explore our guides and tutorials to learn about our core concepts and how to setup Unflow. If you have questions send us a message and we will be happy to help.

Core concepts

Get to grips with the basics and get ready to integrate.

Installation

Add the SDK with just a few lines of code.

Customization

You bring the UI, we bring the data.

Tutorials

Learn how to build a full app with Unflow, or use our components.

Once you’re ready to move on, check out our frequently asked questions, or look at some of our use cases for further examples.


Core Concepts

Unflow is based on a few core concepts, that you can get to grips with quickly. They're spaces, openers and screens.

Spaces

A space is where your content lives. You have a default space and can add as many as you wish to separate your content. For example, you might have a space per page in your app so you can dynamically add content, anywhere.

Spaces are full of openers, and users will only see an opener if they match the rules you've set for it. By default, an opener will be set to show in the space for everyone.

To display a space in your app, see spaces

This example has a standard style space that we show to everyone, in this case showing a big announcement, with a second space that we fill with customised content. Here, we're showing content based on their transactions for the day.

Spaces in action

Openers

An opener is attached to a screen, and serves as the compact visual illustration of it. It has a title, subtitle and thumbnail, and acts as the way users can access content.

Openers are entirely optional if you wish to deliver content automatically.

We have a default appearance that looks like a notification banner, but you can also customize it completely yourself.

You can learn more about openers here

The default opener

Screens

Screens are the primary way in which Unflow content is delivered within your app. They are full-screen takeovers within your app and should be used to convey a single message or promotion. A new Screen can be created and designed from the Unflow web editor.

It is possible to choose different Screen types depending on your use case. Right now, we support Carousels, Articles and Stories.

An example Unflow screen.

Screens have an associated state. By default, when a Screen is created it is in the Draft state. Screens can be changed in the draft state, the updates and content of which is never shown to users in your app.

When a Screen is ready to be included in your app it can be set Live from within your web dashboard. Once a Screen goes live it will appear in your app for users to view.

If a screen is set to show based on events, it will only be shown once per user. This means when testing, you'll have to change your userID between runs to see the same screen twice.

Blocks

Blocks are the most fundamental pieces of the Unflow product. They are editable pieces of content which live inside, and make up most of, a Screen. The initial Block types are Text, Image, Button.

Depending on the type of Block various properties can be configured. Some examples include:

  • The alignment of text
  • Buttons can request permissions or deep link within the app

Ready to start building?

Simplified in-app experiences are just a few lines of code away.

Read the install docs.

Looking to go further?

Unflow is built to help take away some of the inconveniences of mobile develpment, without introducing the issues you could run into with web content. Whilst we think the best way to use our SDK is as we describe in our quick start, we know sometimes you might want to go a little further.

We have options for you to use Unflow simply as a data source for entirely custom views, or to replace the views in our banner for a little bit of customisation.

Learn about custom openers

Tutorials

Formula one sample app