How best to preview a native mobile app that use AEM headless for content | Community
Skip to main content
A
anoopvc1
Level 2
November 3, 2025
Question

How best to preview a native mobile app that use AEM headless for content

  • November 3, 2025
  • 1 reply
  • 114 views

Hi Everyone,

 

How to provide a preview experience (or a WYSIWIG editor) for a native mobile app that uses AEM headless for content delivery? Content is authored on 'AEM sites' pages using core components that expose data as .model.json 
For an SPA or a web app, using the SPA editor or universal editor makes this possible. But how to approach this for a brand that has only native apps and no web presence?


Please recommend any possible or recommended approaches that you might have encountered
Thanks in advance!

1 reply

giuseppebaglio
giuseppebaglio
Level 10
November 4, 2025

hi @anoopvc1, 

Since the native mobile apps consume .model.json outputs from AEM Content Services to render content, a sample approach demonstrated in Adobe's WKND Mobile tutorial shows how a native Android app fetches the JSON for events and maps JSON data to native UI components via POJOs.

https://experienceleague.adobe.com/en/docs/experience-manager-learn/getting-started-with-aem-headless/content-services/chapter-7 

The mobile app can refresh and show updated content by re-fetching JSON after publishing changes in AEM, effectively creating a near real-time preview. By replicating content fragment structures in the app with JSON parsing and UI binding, you approximate a live preview experience native to the app environment.

Here's how I would summarize the necessary steps:

  • Author content using AEM Sites with core components exposing .model.json.

  • Instrument the native app to consume .model.json content endpoints.

  • Reload or refresh content in-app to simulate a preview of authored changes.

  • Optionally run a local AEM instance for development preview.

 
Terms & ConditionsAccessibility statement

Loading footer...