It’s absolutely crucial to choose the right platform for your debut MVP, and be aware of why it’s been chosen. So, the App vs Website battle is on!
For starters, mobile apps are sexy. But should it really be the thing you begin with? Well, the truth is that mobile apps are generally created after the website has been finished, but is this the best decision for your venture?
Based on our experience as a web and mobile app development company in building web, native, hybrid and cross-platform apps for marketplaces, e-commerce and websites, we’ve come up with 10 questions you should answer before deciding on which platform to build first.
This guide will give you the answer to the question – What should I build first – App vs Website?
P.S. If you don’t have time to read the whole article check out the presentation below.
10 Questions to answer before building an app or website
#1 Do you want to reach more users?
A website can help you reach more users in comparison to a mobile app. To prove this, let’s analyze the Google search traffic for a company that provides web and mobile analytics based in the US.
Only about 21% of their website traffic comes from mobile devices and the rest comes from desktop and tablets.
Digging deeper, here we show the two most popular operating systems, where Android users make up 8% (40% x 21%) of all visitors and iOS users make up 12% (57% x 21%) of all visitors.
So, if we decide to just use the iOS app, it’s a rough estimate, we would get about 12% of our current visitors.
Whereas if we decide to go only with the Android app, we (again, very roughly) would only get 8% of our current visitors. Keep in mind there are around 70 different devices using this OS, that you can check by clicking on Android in Google Analytics.
In the battle of App vs Website, when it comes to the user reach, the winner is the Website (this approach is not adaptable to each particular case.
#2 Does your user visit your app +5 times a day?
If you think that your user will be playing with your app a few times a day, then it makes more sense to start with an app. It is way more convenient, faster to access, and keeps users up to date with notifications.
But there is one common barrier that stops people using your app – it’s slow to launch, slow to log in, and slow to perform desired actions.
Things like games, notes, to-do lists, reminders, alarm clock, e-mail or social media – most of them are recommended to have as a mobile app. You’ll use them pretty often during the day and want your interaction with them to be lag-free.
I mean, you don’t want to wait while ‘genius-don’t-forget-ideas’ flood your mind, you want to get them noted down fast. You don’t want to wait 1 minute to play games during your 5-minute bus ride – you want to play them ASAP.
Imagine if you always had to access Facebook through your mobile browser first, then had to sign in, and then finally being able to read that underwhelming message from your friend. Wouldn’t it be better to get an instant notification as soon as you receive the message?
#3 Do you need to access phone native features?
Camera, gyroscope, sensors will always work better with a native mobile app. So, if one of these is crucial for your app, you should consider building a native app NOT a web app.
Nowadays, you can access many of the smartphone’s features with a web app, e.g.:
- smartphone camera using HTML5,
- gyroscope to play games with HTML5,
- geolocation API,
- processing touch events.
Thanks to technologies like NodeJS you are even able to get data in real-time (as it is for native mobile apps). But there are still at least two features you can’t access – geo-targeted push notifications or in-app notifications while using a web app on iPhone (here’s a walk-around for Android users).
Even if your web app has access to some of the smartphone features, it will always provide a different experience than a dedicated native mobile app. Native apps give a better performance – the efficiency of a native mobile app’s processing is higher than a web app’s.
So which is better in the App vs Website here? I think we can say that they’re equally good.
#4 Do you care about app speed?
Mobile apps are faster than web apps. The reason for this is that mobile apps store user’s data settings locally on the phone. Web apps, on the other hand, download the data from servers. In the case of performance, the user’s experience will be best when using native mobile apps.
This time, the App vs Website debate shows App as a clear favorite. You can read more about why web apps are slower than native mobile apps here.
#5 Is your product complex? – E.g. You have data reports to show
Compare these two Google Analytics experiences (see an image below). The first one is when you use a mobile web app to view all those complicated reports. Second is when you have a native iPhone app with an optimized user interface to display all the data.
Without a native mobile app, it would be such a pain to use on your mobile device. Scrolling, editing, reviewing reports with a web app – it’s an absolute nightmare to use a complex page like this on your phone. Properly designed apps solve this problem.
If you are thinking about using your phone for complex reporting, calculations, numbers, then you should know that it will be almost impossible to use these tools without a dedicated app.
This time, the App vs Website winner is the mobile app.
#6 How often is your user going to use your product offline?
Whether you’re in gyms, trains, basements, airplanes, forests, caves, limited access to the internet is always a problem. Because these offline places exist, it brings up opportunities to build complementary, location-dependent apps. Therefore, in this App vs Website battle – App beats web hands down.
When your solution caters mostly for users who are offline-aficionados, then it’s much better to develop an app where the user can access the desired data whenever it’s needed.
Here are some examples:
- Google Maps – nowadays enabling users to download a map to use it with offline navigation.
- Dictionaries – each time you visit a different country you can translate something without an internet connection.
- Tripadvisor – enables you to download a city guide when you are traveling abroad, meaning you don’t need to google the most visited places, best restaurants nearby, or even a map.
#7 Do you have a budget of a minimum of $10k?
If not, it wouldn’t make sense to start developing a mobile app, here is why:
- UI/UX of an app should be adjusted to each platform – Android and iOS apps will always be a bit different,
- development costs around 10-100k $ per operating system,
- the backend should be built with consideration to the web app.
Based on research done by clutch.io the median cost of an app is between 38-171k $. This means in the US the cost will set you back 100-150$ every hour.
If you have 30% users on iOS, 60% on Android and 10% on Windows Phone, you should probably consider developing your app for at least two platforms, and ideally for three.
Developing apps for three platforms means:
- 3 x bug fixing,
- 3 x different development teams,
- 1 new feature = 3 x the same work done for each platform.
It sure is considerable time, resources and money you’ll be consuming, so please don’t attempt to develop an app with only $10k.
In the App vs Website battle, the website gets one back.
#8 Does your product involve navigation or location-based elements? (GPS)
For example, if you plan to build an app for runners to track their route or a taxi app that orders transport to a specific place, the best possible experience you can achieve is with a mobile native app. In this case, a GPS feature is crucial for your business.
So, ding! ding! ding! In the App vs Website showdown, the app takes the round. But saying that, it is possible to do the task with a web app, but it won’t be as fast and easily accessible as a simple mobile app.
Lyft (which is similar to Uber), is a perfect example of a startup phone-app which facilitates peer-to-peer ridesharing. It works by connecting passengers in need of a lift with drivers who are happy to drop them to their destination.
#9 Do you think you’ll be improving = updating your app very often?
If yes, you should definitely go on a website first. Later on, you can invest in cross-platform apps instead of investing in native apps.
Most of the banks, news, and media apps are hybrid because they are web-based. This means that your users rarely have to update the whole application, instead, you just update the website content.
The benefits of this are clear:
- one platform – imagine having to update Android, iOS, and Windows Phone apps all separately.
- no waiting time – you don’t have to deploy the app to the app store which usually takes 1-5 days.
- no correcting issues – you get an immediate result after uploading it on the server.
The average review time for an iOS app is 4 days based on 216 user reviews submitted in 2 weeks. The problem is Apple can reject you if they think your app has:
- substandard UI
- incomplete information
- broken links
If you want to know more about the most common reasons why iPhone apps are being rejected, have a look here. For Android users, it is way faster and easier to do. The waiting time is around 0.5-5 hours.
#10 Does your competitor have an app?
This might be the Unique Selling Proposition (USP) of your business. While you focus on mobile systems only, everyone else will be focusing on web platforms or delivering an average solution for each platform available.
Make it way more appealing and easier to use for the guy with the mobile phone in his hand.
For example, if somebody builds a to-do list app for desktop, tablet, and smartphone, you can just focus on delivering the best possible experience for Apple devices like Clear.
So which should you choose first? App or Website?
Many companies and entrepreneurs want to develop a mobile app first, which may be a huge mistake. I know, it’s a much more sleek and sexy new way to connect with users, but keep in mind those 10 questions above before starting to develop a mobile app.
There are plenty of reasons for both platforms why you should build apps or websites first, so next time do it consciously. Even using modern technologies like node.js can give you a really fast single page application that is accessible on a mobile phone and this should be perfectly fine for your product.
From the title App vs Website, it’s hard to pick a clear winner. Just make sure before setting off on your epic path to develop a mobile app or website, you weigh up all the pros and cons first. If you need some consultation on the matter, don’t hesitate to contact us.
This article is a part of Handbook:Mobile App Development: Guide for Decision Makers
Liked this chapter?
Awesome! We’ll be adding new content on this topic soon. Want to be notified?
Mobile App Development: Guide for Decision MakersFollow handbook