Prompt
How do I reuse one content source across web, app, and kiosks?
Latest observation
Oct 21, 2026
OpenAI APIWeb search: off
A good way to reuse one content source across web, app, and kiosks is to use a headless CMS or a similar content hub that separates content creation from content delivery.
Core idea
- Store content in one place
- Expose it through an API
- Build each channel — web, mobile app, kiosk — as a separate frontend that pulls from that same source
Typical architecture
-
Central content repository
- Articles, images, product info, menus, promotions, etc.
- Managed by editors in one system
-
API layer
- REST or GraphQL API
- Each channel requests only the content it needs
-
Channel-specific frontends
- Web: React, Next.js, Vue, etc.
- App: iOS/Android or cross-platform app
- Kiosk: dedicated interface, often fullscreen and simplified
-
Shared content model
- Define reusable content types like:
- Hero banner
- Product
- Location
- Event
- CTA button
- Each channel can render the same content differently
- Define reusable content types like:
Best practices
- Design for reuse: create modular content blocks instead of hardcoded pages
- Use structured content: avoid putting everything into one rich-text blob
- Add channel targeting: allow content variants for web/app/kiosk when needed
- Localize content if you serve multiple languages
- Version and schedule content for timed campaigns
- Cache aggressively for kiosks and mobile apps
- Provide fallbacks for offline or poor connectivity, especially for kiosks
When channels need different experiences
You can still use one source by:
- Keeping the same underlying content
- Applying presentation logic per channel
- Using channel-specific fields only when necessary
- Supporting overrides for things like image crop, text length, or call-to-action placement
Example
A promotion like:
- Title: “Winter Sale”
- Description: “Up to 40% off”
- Image
- Start/end dates
- CTA link
Can be:
- A large web banner
- A compact mobile card
- A fullscreen kiosk slide
All powered from the same content entry.
If you want a practical stack
A common setup is:
- Content source: Contentful, Strapi, Sanity, Directus, Adobe Experience Manager, etc.
- API: GraphQL or REST
- Web: Next.js
- App: React Native or native
- Kiosk: Web app in fullscreen or a native shell
If you want, I can also show:
- a reference architecture diagram,
- a sample content model, or
- a recommended stack for your specific use case.