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…

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…

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 to register a custom Gravity Forms field type for the mobile app. Requires two hooks: mam_form_manager_process_field_type_{type} for build-time and a corresponding submit-time handler. Forgetting one breaks the round trip…

How forms-manager caches Gravity Forms definitions for the phone-data pipeline, why it’s keyed by form id plus relevant settings, and the symptom-and-cause for stale-cache ‘app shows the old form’ bugs.