End-to-end trace of an app form submission: AJAX POST → mam_gf_processing_form → field validation → mam_for_gravity_forms_form_submitted_{id} → result envelope → mam_form_manager_send_notifications.

How mam-main supports multiple form providers (Gravity Forms today, programmatic forms today, additional providers like Ninja Forms via the same extension surface). Explains the two parallel hook namespaces — generic…

A worked example walking a single form from declaration through submission: the mam_gf_get_form_settings entry, slug→field-id admin mapping, cache pre-warm, dynamic data injection, the three row→form surface patterns, and the submission…

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.

The three patterns a content row can use to open a form: tabbar button, custom_form_array on a row, and content_type=form tap. Each path’s data shape, the iOS resolver site, and…