Home page
“Why do we even need a mobile app at all?”
“Can we just make a really good website or does it need to be an app (native)?”
I have been asked this kind of question a few times over the years, and considering my current role as product designer specifically on a mobile app, it’s in my best interest to be prepared whenever it arises.
“Why do we even need a mobile app at all?”
“Can we just make a really good website or does it need to be an app (native)?”
I have been asked this kind of question a few times over the years, and considering my current role as product designer specifically on a mobile app, it’s in my best interest to be prepared whenever it arises.
The answer may differ from team to team. Depending on what stage your company is in, what specific product requirements you may be working with, if it is a net new product or it’s an existing product that is being addressed. These are all considerations that may define the feasibility of leaning toward web or toward native. Self preservation aside, I firmly believe that building for native is the best option for a team that values product quality and the user experience. Below we’ll walk through 6 reasons that might convince you of the same.
Native apps are available to open on the very top surface of your devices as soon as you unlock them – on your phone screen, your desktop, or your dock. Access is unmatched relative to the web, where you need to open a browser to facilitate the usage of your app. Not only that, interconnectivity within the use cases that your app solves for becomes noticeably denser. In leveraging native-only features like notifications, lock screen widgets, home screen widgets, and more, the gaps between your customer’s intent and the value that your product provides close and product usage begins to feel faster, more seamless and more convenient.
Initiate user engagement with a smartly timed push notification, or use Back Tap to trigger a nifty Shortcut you’ve spec’d for your app. Rather than a user directly going to your website to visit you on a whim or via a prompt email, you are able to show up at the exact right moment (with the right data and use cases) to the user in ways that make sense to them.
Native apps come with the major benefit of having utility despite not being connected to the internet. Imagine if the camera app on your phone, or the calculator app on your laptop, was only available when you were connected to the internet. This has the dual effect of maintaining a baseline level of utility at all times, but also keeping data available locally even if you’re offline.
Consider examples like your photos from the Camera app, your medication schedule or other important medical advice that’s saved within a medical app, or maybe it’s order data that you need to reference while attempting a return at the store. Access to this data can vary in its critical nature, but are consistent in the convenience and value it brings to the user.
Apple and Google have wide ranging suites of powerful platform technologies available for developers that aid in smoothing the experience of using your product. There are three categories that are useful to consider:
Interactions and data
Some of the most useful integrations include thing things like gestures, accessibility features, navigation, location data, motion and health data
Powerful out of the box components
There is a level of predictability and standard with the components that Apple and Google provide. With teams of hundreds of talented designers, engineers and product folks working on these foundational parts, you can safely assume a level of care and maintenance that doesn’t necessarily come with other pre-configured libraries. The effort required to provide flexible, scalable components that match your user’s expectations becomes significantly reduced, leaving more time for actual problem solving and craft.
Complimentary system-level integration
Going back to that very top layer of access within your devices (think of the dynamic island, or your lock screen widgets), the platform technologies provided by Apple and Google here allow you to expand the breadth of where your app is accessible from and include useful shortcuts for users to quickly access.
A common argument that used to arise was that the expense of hiring multiple developers to build and maintain two separate codebases for Android and iOS was too expensive. With the advent and wide adoption of React Native and Flutter, this issue doesn’t stand as firm anymore.
React Native allows you to build native apps off of one central codebase.This is an accessible option for new teams who wouldn’t need to refactor and migrate their entire codebases but has also been adopted by big players in tech (Discord, Amazon photos, Coinbase). No more two entirely separate code-bases to maintain between iOS and Android. The time it takes to stand up a quality, feature rich native app across Android and iOS has been significantly reduced. There are still some more time intensive parts of the native development process, such as QA and AppStore/ PlayStore approval processes, but when comparing all of the other value that native platforms provide over the web, the question becomes less straightforward than it used to be.
Connecting to devices like smart watches or other wearable tech can unlock an entirely new range of data and features for you to leverage and provide for your customers. Think activity or health apps that track your movement and vitals, or maps where you can quickly glance directions on your watch as you’re walking or riding.
If we were comparing the web app experience to that of a well-built native app, in terms of car brands, it’s like comparing a Lexus to a Dodge. Both cars are going to get you where you need to go and most times one will do so noticeably smoother, faster and more reliably. In more complex interactions like gestures or accessibility tools in products like maps, shops or video streaming, the native experience really shines against comparable web experience. Consider the different experiences in using Google Maps embedded in a mobile browser vs. using the native Google Maps app. The difference is stark.
When we look at the human experience of using software, it all starts with the physical interaction between you and the device. Unlocking your phone, tapping your keyboard, shifting your mouse, swiping or tapping with near-zero-latency. Designing software requires us to consider the user’s baseline expectations of how those types of interactions will feel. Our output is meant to feel as natural of an addition to the human-to-software experience as possible. Natural. The most important thing to consider is not necessarily what core functionalities might change if you chose web or native, because those are limited, but to consider how well those functionalities might operate and how natural they might feel one way or the other. Then, as an extension of that, we need to consider how we’re limiting the kind of dimensions that we can approach our products at. What angles are we possibly sacrificing by selecting web over native? Physical angles like connections to smart watches, or heart rate monitors, or digital angles like useful widgets or quick actions. What are we risking by encasing our product within a web browser?
Alternatively, from a more neutral standpoint, you might start by finding out what the biggest risk to your success as a business is. If the answer is time, or money, then at least starting with a web app may be necessary. If time is your friend, the next question to answer is: What actual problems are our customers facing, and how are we planning to solve them? If you know the answer to this question then you’ll have a good idea of the functionality required to stand up something that provides value for them. That’s the ultimate goal; build something that people find useful. If there’s nothing within those bounds that require native-only functionality (offline utility, health data, biometrics, robust AI features for example), then I might seriously consider sticking with the web.
As time goes on and technology advances, the web is becoming more flexible and lightweight, but native platform technologies, those accessible through XCode and Android Studio, are also growing to provide more intuitive and natural UI options and even greater breadth around tuning your hardware (keyboards, mice, phone buttons and surfaces) to act as direct interacting nodes to your product’s features. In most cases, pursuing web or native isn’t a make or break decision, but if we’re looking at product design through a lens that values continuity and fluidity between the real world and the software we use - between your hands (among other extremities) and your devices - then native apps truly are the way to go.
Thanks for reading.
Nat
Sometimes wedostuff forfun Sometimes wedostuff forfun Sometimes wedostuff forfun
Sometimes wedostuff forfun Sometimes wedostuff forfun Sometimes wedostuff forfun
Thanks for stopping by.
Care to chat? Please reach out at
timomarigreen@gmail.com