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…
Why most changes you make reach users right away, while others need a whole new App Store / Play Store build — and what those version and build numbers are…
How MAM stores, resizes, and serves your app’s images — the branding art generated when you publish, and the content images served straight from WordPress.
Every button in your app is backed by a content class — here’s what that means, and how to reason about which of the 19 types to pick.
Why MAM’s button types share a duck-typed six-method contract, what each method does, and how the methods split between the admin builder and the device payload.
Can't find the answer you're looking for? Don't worry we're here to help!