Mobile App Settings
This page is the field-by-field reference for Eventonomy → Settings → Mobile App. For what the companion app actually is, what the plugin provides versus what the app provides, and what members can do once connected, read Mobile App first - this page assumes you already know the concept and only documents the settings.
What You Will Learn
- Every field on the Mobile App tab, its default, and what it controls
- What happens when a field is left blank
- When a setting takes effect on a member's phone
Where to Configure
Go to Eventonomy → Settings → Mobile App. The tab holds a single Mobile app card with eight fields. All eight are present in the Free plugin - the app connecting at all is the part that needs Pro and a valid licence.
Settings Reference
| Setting | Default | What it does |
|---|---|---|
| Enable the mobile app | On | Your half of the connect gate. When off, the site tells the app it is not available and the app will not connect. When on, the app is still only reported as available if Eventonomy Pro is active with a valid licence. |
| App name | Blank | The name shown inside the app. Blank falls back to your WordPress site title. |
| Accent color | Blank | A hex colour, for example #4d7c0f, that white-labels the app palette. Blank falls back to #4d7c0f. |
| Logo URL | Blank | Shown on the connect / sign-in screen. Blank falls back to your WordPress site icon. If you have no site icon set either, no logo is sent and the app shows its own placeholder. |
| Sign-in background URL | Blank | An optional background image for the sign-in screen. Blank means no background image is sent. |
| Terms URL | Blank | A link to your terms of service, shown in the app. Blank means no terms link is sent. The privacy policy link is separate and is never entered here - it always comes from the page you set under Settings → Privacy in WordPress, and only once that page is published. |
| Minimum app version | 1.0.0 |
The oldest app version allowed to connect. Members on an older build are prompted to update first. |
| Enable push notifications | On | Tells the app that push is available, so the app asks the member for permission and registers their device. Turning it off stops new devices being registered. |
Notes on Individual Fields
Enable the mobile app. This is deliberately a two-key gate. Your toggle is one key; a valid Eventonomy Pro licence is the other, and both must hold. The check is fail-closed - if the licence lapses the app is refused at connect time even though the toggle is still on. See Licensing.
Blank means default, not empty. App name, accent colour and logo all fall through to a sensible site-derived value when you leave them blank, so the app never renders nameless or unbranded. Clearing a field you previously filled restores the fallback rather than blanking the app.
Terms URL and the privacy policy. Only the terms link is yours to enter here, and it is blank on a new install, so nothing is sent until you fill it in. The privacy link is read from the WordPress privacy page instead - and it only becomes a real link once that page is published. WordPress creates the policy page as a draft, and a draft has no public address, so a site that has selected a page under Settings → Privacy can still be sending the app nothing. Publish the page, then check it opens for a logged-out visitor. Both links are blank by default and app stores generally expect both, so this is a launch step, not a nicety - the full walkthrough is in Mobile App.
Minimum app version is a floor, not a version you are publishing. Raise it only when an older app build genuinely cannot work with your site, because everyone below it is locked out until they update.
Enable push notifications controls registration, not delivery. Switching it off tells the app to stop registering devices, but devices that already registered stay registered and can still receive a push. To stop a specific device, the member signs out or uninstalls, which removes it.
When Changes Take Effect
These settings are read when the app fetches its configuration, which it does on connect. A branding or gating change therefore reaches a member the next time their app asks the site for its configuration, not instantly on the device they are currently holding.
Related
- Mobile App - the conceptual overview of what the app is and what members get.
- In-App & Push Notifications - what the bell and push deliver, and how they sit alongside email.
- Licensing - keeping the licence valid so the app can connect.
- Mobile API Contract - for developers: exactly what these settings send to the app, and what the plugin does not handle.
What's Next?
See how push and the in-app feed fit into the rest of Eventonomy's notifications.