both
-
How a MAM app is structured: tabs, screens, buttons, and content classes
The mental model behind every MAM app: a tab bar and left menu made of buttons, each one backed by a content class that renders a single screen.
-
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.
-
Content source vs. global settings: where a button’s data comes from
Every button draws on two kinds of input: its own per-instance content source, and the site-wide global settings that style and gate it.
-
App settings vs plugin settings: where each knob lives and why
Why MAM splits your settings into two families — app settings that ship to the phone and plugin settings that stay on the server — and how the app-settings side…
-
Push notifications aren’t arriving
A step-by-step way to track down why push notifications aren’t arriving in MAM Suite — from credentials and device-token registration to cron queue draining, opt-out flags, and iOS/Android platform quirks.
Knowledge Base Categories
Need Support?
Can't find the answer you're looking for? Don't worry we're here to help!
