AppNatively is a powerful, modern plugin for WordPress that bridges your website with the AppNatively mobile app builder. It automatically generates high-performance REST API endpoints for your WordPress data, enabling you to build premium, fast, and fully-synchronized native mobile applications.
Whether you run an online store, collect leads through forms, or publish a directory of listings, AppNatively detects the plugins you already have active and integrates deeply into your setup to power mobile cart operations, product catalogs, order tracking, form submissions, listings, and customer accounts natively.
craf_appna_integrated_plugins filter.E-Commerce
Forms
Directories
AppNatively provides REST endpoints read by your mobile app and AppNatively Studio. Notification delivery uses the configured AppNatively notification service.
To support website previews in Studio, the plugin automatically loads AppNatively’s website preview script on public-facing pages. This browser request occurs before notification pairing and is independent of the API switch. Fetching the script sends the visitor’s IP address and standard browser request headers to appnatively.com; referrer information depends on the site’s and browser’s referrer policy. Website preview is separate from notification delivery and its sending setting.
Push notification sending is on by default. You can turn it off at any time under AppNatively Notifications: uncheck Send notification events and click Save notification settings. Existing saved opt-outs remain off. Turning sending off stops new notification requests and cancels queued work; an in-flight request may finish. The API switch also stops notification delivery.
Use Check Connection in Studio to pair notification delivery. Send notification events is the only on/off control for notification sending; there is no separate data-sharing checkbox.
While sending is on and Studio is paired, WordPress and supported plugin hooks queue order, listing and form submission IDs/statuses, related user IDs, account roles and login-session revocations. Authenticated service requests can read names and email addresses for audience display. Built-in form events do not include submitted field values. Raw login tokens and passwords are never sent. Custom event emitters control their own payloads and must disclose any additional data they send.
A background queue performs notification delivery using AppNatively-prefixed WordPress queue storage and cron/loopback requests. Native user records, cookie sessions, orders and listings are not modified by notification listeners. Business events expire after 24 hours. Session revocation jobs expire with their source session; other account events expire after 30 days. Successfully processed jobs are removed. HTTP configuration errors pause the affected source/channel for manual retry, and expired paused jobs are removed by the queue health check. Credentials are encrypted locally and removed on uninstall. Notification capture failures do not fail native actions; transient events may be lost when local queue storage fails.
Service links: AppNatively, Privacy Policy, Terms of Service.
%postname%, such as Post name (Settings Permalinks), so content links resolve correctly in the app.zip file.Alternatively, unzip the file and upload the appnatively folder to /wp-content/plugins/ via FTP, then activate it from the Plugins screen.
https://yoursite.com), and paste in the connection key.If you activate a supported plugin after connecting, reload the Website Connection page so the new integration appears in the plugin list.