-
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.
-
Tab bar vs. left menu vs. home buttons: choosing your navigation model
Your app gets three separate navigation surfaces — home buttons, the left menu, and the bottom tab bar. Here’s what each one is for, and how to put them together.
-
The entitlement model: how plugins gate themselves on license and version
How MAM Suite sibling plugins decide whether to run: the mam_plugin_entitlement filter, an async-synced cache, fail-open behavior, and version checks.
-
The forms manager: providers, lifecycle, and why Gravity Forms is the engine
How MAM Suite turns WordPress forms into native app screens — the provider abstraction, the submission lifecycle, prefill paths, and where Gravity Forms plugs in.
-
The home screen stack: how blocks, sections, and ordering compose a layout
How your app’s Home screen comes together from an ordered list of stacked sections, category rows, and a few pinned blocks — rendered top to bottom, exactly as you built…
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
