Why are they still such a popular request when we’re well served by web browsers and responsive themes these days?
Is delivering a mobile app a huge amount of work to develop and maintain?
The many forms of mobile application
Any website being developed these days is built on top of a responsive framework allowing pages to adapt and re-layout content based on the size of the viewing device.
Perfect for mobile and tablet devices alongside traditional desktop screens.
So why are mobile apps still chased after by people?
What’s wrong with their responsive website?
Often the case is simply about being present on a person’s phone screen - an icon shining back at them as a reminder about the service available. Many website companion mobile apps are nothing more than a re-purposed pile of content from the website or a form-based user interface to search the information from the website.
So if the desired mobile app isn’t technically demanding what’s the best way to get it built and deployed so that your customers or visitors can benefit? There are three directions you can take...
Apple (iOS) and Android devices have their own flavour of a mobile app, also known as a native app, which is the best possible way to deliver a great mobile experience making full use of the hardware in someone’s pocket.
However, the time and cost to find dedicated skilled developers and maintain two versions of a mobile app, which is often a simple companion to a website, is often out of the reach of most project budgets.
It’s one set of code and a much simpler development process that can often be implemented by the same team that built the website. There are many toolkits and templates to generate simple applications such as Cordova and ReactNative.
It’s the quickest way to get a mobile app deployed and your icon on a user’s phone screen.
Where does a CMS like Drupal fit into this?
A digital experience platform (DXP), such as Drupal 8, works as a great content store thanks to its built-in data modelling toolkit. But what makes the Drupal CMS shine is the ability to expose the data model via industry-standard API formats such as RESTful, JSON and GraphQL - meaning whatever type of mobile app is decided on - the backend content that powers your mobile app can be driven by Drupal and kept separate from your app.
This is commonly known as running the CMS in Headless mode if it is not also powering the website.
Where to go first?
Drupal has a variety of mobile app approaches freely available to use, modify and learn from. Although some of the content is a little out of date, the Drupal.org site has a reasonable summary of options. Some pointers to get going for each type of mobile app are:
No matter what form of mobile app you decide on, Drupal 8 provides a solid platform for serving your data to a multitude of user interfaces - be in mobile apps, websites, smart televisions, information boards or simple input into another system.
The components and plugins needed are mostly bundled with the default Drupal install - or a free simple module installation away. There’s nothing stopping you getting stuck in with some experimentation to decide where you want to head with Drupal as your backend.