explanation
-
Roles and audiences: how per-role settings shape what each user sees
Why MAM is role-aware, how the per-button/per-role/global cascade resolves a setting, and how anonymous, member, owner, and admin audiences each get a tailored app.
-
The publishing pipeline: from app settings to a store build
How Publish Your App turns your saved settings into a Fastlane CI build over on WPMAM’s servers — a request-then-pull, fire-and-forget flow where you check on progress by polling, not…
-
Push notification credentials: APNs and FCM for non-developers
What APNs keys, FCM service accounts, and device tokens are, and how MAM Suite uses them to deliver one notification to one phone.
-
The phone-data pipeline phases: auth, settings, content, finalize
Why the mobile-app JSON is built in four ordered phases, what state the context object carries through them, and where your subscriber runs in the sequence.
-
Previewer vs. published app: what’s the difference
Why the Previewer updates the instant you save a setting, while your published store app is a separate, branded build that has to go through Apple and Google first.
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
