Saved buttons reference content classes by name through a global registry, so renaming a class silently orphans every site’s saved buttons unless you migrate them.

Sibling plugins never import mam-main classes; they hook its filters and actions. Why that decoupling is what lets MAM Suite scale to 9+ plugins across ~2K sites.

How MAM authenticates app requests from a device pid, why app AJAX leans on a soft-nonce model, where capability checks live, and who sanitizes input.

Why a setting resolves to the value it does — the per-button, per-role, and global fallback chain behind mam_app_settings_get_setting, and where to write.

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.