Interpretations of a mobile CMS
When somebody says “Mobile CMS” they could actually have a few different things in mind, raising a few complications towards the concept – there are various interpretations of what a mobile CMS is. The following are the 3 most common interpretations of what a mobile CMS is:
1. A CMS to manage content in native mobile apps.
For example, you have an app for iOS and Android, where users are able to purchase cars. You would like a CMS that stores all relevant car information and delivers it to your app on both mobile platforms. This could be seen as a mobile CMS.
2. A CMS to manage content in mobile responsive websites.
Let’s take the previous example and say that, in addition to your iOS and Android apps for selling cars, you also have a website that people visit from various mobile devices. You may or may not have a native mobile app, or users may not wish to download another app, making it necessary to have a mobile “optimized” website. In this case, your CMS needs to support content delivery to all possible screen sizes, aspect ratios, and resolutions, across smartphones and tablets. A CMS for such mobile responsive websites could also be seen as a mobile CMS.
3. An application running on a mobile platform that allows a user to manage an existing CMS instance.
For example, you have a news website that you built with WordPress. You would like an application for your Android phone to be able to add new articles and update existing news stories as they develop on the go, taking a part of your website and injecting it into a mobile app. This could also be seen as a mobile CMS.
Therefore, when talking about Mobile CMS, especially when making decisions within a team, it is important to make sure everyone’s on the same page.