USE CASE — MOBILE APPS

A Typo Fix Shouldn't Wait on Apple's Review Queue

Anything hardcoded into your app binary is hostage to app store review, while content served from Zunoy's API changes the moment you publish — no build, no review, no wait.

Start Building Free

Ten field types, including relations

Draft states before every release

One content model, every client

What's Actually Worth Hardcoding

Hardcoded in the binary

A copy fix means a new build and a review cycle

A promo banner is stuck until the next release

Content lives in two places — the app and the website

A copy fix means hitting publish

A promo banner updates on its own schedule

One content model, read by both

What Actually Transfers to a Native Client

The parts of the platform that matter to an app are narrower than what matters to a website, but they carry over directly rather than requiring a mobile-specific rebuild.

Ten field types

Model app content properly, including relations and repeaters.

Transformed media

Request exactly the image size your screen density needs.

Draft states

Stage a change ahead of a release without exposing it early.

SHARED CONTENT MODEL

One Content Model Instead of a Website's and an App's

A team running a website and an app separately usually ends up with two content systems that quietly drift apart — the same promotion worded slightly differently on each. Zunoy serves both from one model, so there's only one place to get it right.

One Entry, Every Surface

One entry, read by the site and the app alike

One Admin, One Model

One admin, one permission model, for both surfaces

Draft Until Ready

Draft states let app-specific copy wait for the right release

Common Questions

Does Zunoy have a native mobile SDK?

No. Zunoy exposes a standard REST content API over HTTP. Any mobile networking library capable of making an HTTP request and parsing JSON can consume it, without a dedicated SDK.

Does updating app content require going through app store review?

Only for anything hardcoded into the binary. Content served from Zunoy's API updates the moment you publish, since it's a data fetch on the app's next request, not a new build submission.

Can a website and a mobile app share the same content?

Yes. Because Zunoy is headless, the same content model and entries are available to any client through the API, so a website and a native app can read from one source instead of maintaining separate content.

Can app-specific copy be staged ahead of a release?

Yes. Entries stay in draft until published, so copy tied to an upcoming version can be prepared in advance without appearing through the live API before that version ships.