MAM_Phone_Data_Pipeline is the canonical builder of the mobile app’s JSON payload. 4 phases (auth → settings → content → finalize), state carried by MAM_Phone_Data_Context, ~70 sibling-plugin subscribers via the legacy…
How mam_forms_manager_phone_manager normalizes phone numbers, validates them via SMS-delivered codes, and ties into both Gravity Forms phone fields and the user-roles phone-code login flow.
The Left Menu Separator content class — visual divider for the left-side navigation drawer. Renders as a horizontal rule or a labeled section header.
Reusable UI section builders that content classes assemble into per-screen output. 15 filters covering add-to-cart, featured-image, social-media, chat config, order details, and more. Loaded from includes/content-class-elements/general-elements.php.
How mam-main bridges Gravity Forms into the mobile app: form discovery, the cache layer, mobile-shape transformation, the per-form-id submission hooks, and the route from submission to mam_form_manager_send_notifications.
Can't find the answer you're looking for? Don't worry we're here to help!