Mobile and apps
This page is for owners who are asked "should we have an app?" or who want the site to work better on phones. Exponential offers responsive designs, a REST content API, personal API keys and OAuth for apps, remote services, feeds and an optional browser navigation cache for repeat visits (Mobile and headless for businesses). Most organizations should get the phone experience of the website right first.
Contents
Website first
A responsive site works on every phone without an install. Check yours regularly:
- To do: The front page, an article, a form and the search work on a phone.
- To do: Images are not larger than needed; pages load quickly on a mobile connection.
- To do: Buttons are large enough and forms are easy to fill in.
- To do: Text can be zoomed to 200% without sideways scrolling (Accessibility upkeep).
The business test plan is on Responsive sites. Editors can work on a phone too: the administration has responsive designs (admin3 responsive admin).
The channels at a glance
From Mobile and headless for businesses:
| Channel | What Exponential offers | For owners |
|---|---|---|
| Visitors on phones | responsive public designs | Responsive sites |
| Your own app or front end | the REST content API, read at v1 and v2, write at v2 | The REST API for owners |
| Programs and integrations | personal API keys, OAuth2 for apps, remote service tokens | Apps and API keys |
| Remote administration, portals, scripts | over a thousand named remote services | Remote services (expservices) |
| Feed readers and podcast directories | RSS, Atom, OPML and Apple Podcasts exports | RSS and podcast feeds |
| Repeat visitors | an optional navigation cache in the browser | Offline and repeat visits |
Before you commission an app
| Question | Why |
|---|---|
| What can the app do that the website cannot? | an app is a second product to maintain |
| Does it only read content, or also write (comments, orders, forms)? | writes need v2 of the REST API or remote services, and careful permissions |
| Do its users sign in? | apps whose users sign in use OAuth2; a program acting as one user uses an API key (Apps and API keys) |
| Who builds and updates the app for each new phone operating system? | the app is not part of Exponential |
| What happens when the site is in maintenance? | the app depends on the API being available (App backend reliability) |
| Which content may the app show? | the API applies the same policies as the website |
Plan it like any integration: Planning an integration.
Who does what
| Task | Who |
|---|---|
| Decide the channels and what each is for | owner (Mobile strategy) |
| Build and publish the app | app developer or partner |
| Create the app's credentials and limit them | administrator |
| Keep the content right | the editorial team, as for the website |
| Keep the API available, monitored and backed up | host or partner |
Keeping it running
- Review the app's credentials once a year with the access review: keys are revoked by the owner or an administrator, and end when they expire or the owner is disabled (Personal API keys).
- Tell the app developer before upgrades; ask your partner what changes for API clients (REST API v1 and v2).
- Use the Mobile checklist before each app release.
Related pages
- Mobile and headless for businesses
- Headless with the REST API
- The REST API for owners
- Free documentation: this page is free to copy, translate and improve under the GNU FDL 1.3.
Become an Exponential Partner
Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.