Does your business need a mobile app?
Owning a website is a given. But a mobile app is another ball game. The cost of developing a mobile app is significantly higher than that of a website. After the initial investment, it requires skills beyond those of a web developer to maintain. Kachingching!
There are several reasons for you to consider owning an app – managing operations, sales, client support, internal training, client education, communications unification and so much more. The incentive is obvious – immediate and constant connection with your target audience or at will.
Let’s take a look at a few example scenarios and potential benefits:
Operations: You can automate many routine tasks using machine learning. This drives down your overheads while giving you the capacity to handle more work. You could even double your client portfolio without increasing your labour footprint. Big savings and happier customers.
Internal Training: One of the most crucial aspects of running a business is continuous staff training. Training can even be more costly if you have to send your staff to offsite locations. Accommodation, transportation, and food expenses often discourage some businesses from providing as much training as they really need to.
By creating an on-demand app that automates the training process and tracks and reports the progress of each team member, you’d save a lot of money and ensure better compliance.
There’s no sure way of telling if an employee learned anything from a 3-hour seminar 3,000 miles away. But if you automate the process with an app, you can create a comprehensive assessment that monitors their understanding and progress. You can even enable questions and discussions. They can take the training lessons from anywhere, even from the comfort of their homes. And that’s not on your bill!
Client Education: Depending on the nature of your business, you may need to conduct client education sessions. If you are doing that onsite, you have to consider space, power, airconditioning, personnel, and refreshments. All those are overheads. The funny thing about this though is that the presentations are usually 100% identical. You’d be spending money to repeat the same story to a different audience!
In this case, a mobile app that automates the process can help you remove the need to entertain people at your office for routine product education. You can record the training once and only change the content when an update is necessary.
So, again, depending on the nature of your business, you may greatly benefit from owning a mobile app.
So, should you create a website or build a mobile app?
Let’s start with the fallacy that deploying to multiple platforms using Apache Cordova/Phonegap cuts your development time to the cost of one platform. Different platforms may have different web view renderers, and bugs may exist on one platform and not the other. You have to keep a constant watch on each platform, and if you don’t quickly address bugs on one platform, be ready to pay the price in poor reviews. Moreover, fixing platform-dependent bugs in hybrid apps can take longer than native apps due to requiring some kind of workaround.
Using hybrid technologies, optimistically you can cut the initial build time to 75%, but when you factor in the lifetime cost, the total cost of maintaining your app becomes much pricier than most entrepreneurs are prepared for. In almost every single scenario we’ve seen, it makes more sense to start with a single platform (choose one out of web / iOS / Android) and validate your prototype first with a very soft launch and finish debugging before moving on.
But how do you decide between a mobile app or a website? The remaining questions are meant to help you answer this.
1. Is a core feature based on native functionality?
There are certain features within mobile apps offer that are such huge advantages over web that they tip the scales in favor of starting with a mobile app. A few that come to mind are geolocation using the phone’s GPS, push notifications, real-time tracking, offline data storage, or integration with native tools like Google Fit / S Health / HealthKit.
Yes, it is possible to use HTML5 to tap into some of these via a browser, but you might actually end up spending more time getting it to work well in HTML5 than native. Remember that the advantage of developing a browser-accessible website is about functioning on a lot of different devices and browsers, and not competing with mobile apps on native functionality.
2. Does creating a mobile app take advantage of a market opportunity?
I’ve seen some websites out there that would make perfect mobile apps, except the years go by and they still don’t have one. This may be a perfect opportunity to take some version of an idea that’s already been validated, do it better, and bring it to the app store. (This begs a reminder that someone out there has already thought of your brilliant idea — winning is about execution.)
For example, maybe there’s a location-based RV parking sharing app that hasn’t hit mobile because it’s not a sexy industry. This market would be begging for a mobile app since it’s the perfect marriage of under-the-radar and the audience being entirely mobile since they’re always on the go. Creating a mobile app here would make much more sense than a website.
3. Is pay-to-use rather than recurring revenue your primary monetization?
If you’re convinced that your primary revenue will come from users paying once to unlock your app, this form of monetization is commonplace for mobile apps yet hasn’t flourished for websites. On the other hand, the web has an advantage when it comes to recurring revenue, where Apple and Android both take 30% of your revenue for in-app purchases and subscriptions. (Some argue that the free visibility of being in the app store gives you visibility that makes up for the 30% loss, but your app stands a fat chance of getting featured in the app store without App Store Optimization, which basically means you still have to pay for marketing help.)
If you answered no to all 3, then start with a website due to lower development costs.
Just try to build the website with companion mobile apps in mind by starting with an API backend and separate frontend like Angular or React. Doing it this way is not substantially more expensive than say doing it entirely in Ruby on Rails, but this way, if and when you decide to build a mobile app, you can reuse the same API, and maybe even some of the frontend code as well. If you need more guidance with the web development process, read our Ultimate Guide to WordPress Development.