Introduction to Mobile CMS
As consumers have access to the internet via many different platforms, it is important to be able to both distribute and manage content to each, whether it be IOS or Android, a website or on-the-go in the most efficient and effective way possible.
Multi-Channel Content Delivery
This is where content can be managed in one place but is still able to deliver to different devices such as smartphones and tablets. This can be presented accordingly despite being in raw format (Microsoft Word, PDF, HTML).
Accommodating Template System
This feature moves away from traditional CMS templates. A Mobile CMS has to adapt to new devices with different functions and restraints. These templates can be adapted in 2 ways.
- Multi-client is where the template depends on the users device and all versions of the site are at the same domain.
- Multi-site is where a targeted sub-domain is used.
Location-based content allows a business to capitalize on the fact people carry their mobiles most places they go. If they share their location data then it presents an opportunity to send personalised ads, information or news based on the location tracked by GPS (global positioning system) for example.
This approach means that when trying to update an app or add more content, it must be done manually for each app. This time constraint then leaves a delay in the delivery of the content. Once these changes are made they then need to be resubmitted to the app store which again adds to the delay.
Separate content and presentation
This means that developers have the ability to use whatever tools they need to present specific content on any given display.
Content processed in accordance to apps
Whether it has to deal with network connectivity issues, data transferring and fast paced efficiency with opening assets.
The infrastructure must do its job so that developers can work at speed and to a timescale.
This blog explains in more detail the up and coming importance of API's
A headless CMS is a back-end only content management system (CMS). A RESTful API means content can be displayed on any device. It cuts the front end from the back end. It outperforms a traditional CMS in different ways. This can be through platform independence, cross-platform support, developers are put first and coding is far simpler.
It is also an advancement from traditional standalone websites and makes the separation of content and presentation available. It can power the likes of SPAs and mobile apps using shared data to personalize the user experience. They significance of this personalization is that the channels and devices have the same data but can be edited separately.
Read more about the advantages and disadvantages of a Headless CMS architecture.
Headless Content API
The Headless Content API is a generic REST API running on top of the Bloomreach delivery tier, automatically exposing all published content in Bloomreach's content repository based on the document types.
Headless Experience API
Bloomreach offers a unique way of integrating Single-Page Applications (SPAs) such as Angular and React with the CMS. In this approach the SPA is still powering the delivery, offering great flexibility to IT. While at the same time CMS users can use all of the powerful features that come with a modern CMS: preview, in-context editing, drag-and-drop page composition, personalization, and more.