[ruckstar]

It's both a no-code tool for building native mobile interfaces AND a platform for hosting/serving them remotely (i.e. server-driven UI). It doesn't make sense to use this for your entire app but it's an invaluable tool for certain use cases.

We're still playing with our marketing language. Very interested in feedback on how you'd position this.

[danpalmer]

I was quite confused as well. I assumed from the beginning that this was a tool for building a whole app, and I was confused about why there was no App Store/Play Store process involved, and how any backend logic would work.

What I understand now, and where I see the value, is in this being a low-logic CMS – i.e. you can do a lot more than a flat article, but you likely wouldn't build a full app with it.

I can imagine us (as an iOS team) adding this as our Blog section in the app, and handing over responsibility for all the design, navigation, interaction, and articles, in it to our content team. They might even make our article much more interactive with this (quiz idea is great!). Currently they use a regular CMS for posts and we handle all the information hierarchy which isn't ideal.

[ruckstar]

Great feedback, this is really helping us understand how to improve our messaging. The blog section in your app is a great use case.