APPNATIVELY
AppNatively compatibility with REEID Translate
AppNatively compatibility with REEID Translate is being evaluated from available plugin evidence. Provides a WordPress-side REST API layer that is consumed by the AppNatively mobile app builder and AppNatively Studio (endpoints are generated for WordPress data). No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for AppNatively.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
AppNatively is documented in the Other category with 8 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How AppNatively compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Provides a WordPress-side REST API layer that is consumed by the AppNatively mobile app builder and AppNatively Studio (endpoints are generated for WordPress data).
- Supports deep integration with e-commerce plugins via a unified e-commerce API, including standardized endpoints for products, categories, shopping carts, and order details (WooCommerce, FluentCart, SureCart listed).
- Supports form plugin integrations by rendering and submitting existing forms natively inside the app (multiple form plugins listed).
- Supports directory/listing integrations to provide native browsing and detail screens for listing directories (multiple directory plugins listed).
- Includes an admin settings screen to control API access: can switch the API off entirely (uncheck “Answer requests from the mobile app”) without deactivating the plugin.
- Uses a “connection key” in AppNatively Studio to authorize Studio to read which supported plugins are active on the site; the key can be rotated/revoked from the plugin settings.
- Allows ending app user sessions via “Sign out all app users” and supports signing out individual accounts via password change (as described in FAQ).
- Is extensible for developers to register additional integrations using the `craf_appna_integrated_plugins` filter and category-specific filters (`craf_appna_ecommerce_integrations`, `craf_appna_form_integrations`, `craf_appna_directory_integrations`).
CONTENT BOUNDARY
AppNatively capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
AppNatively and REEID Translate FAQ.
What does AppNatively do according to the available plugin evidence?
AppNatively has 8 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for AppNatively?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for AppNatively?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate AppNatively in a multilingual WordPress workflow.
REEID documents AppNatively functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.