Native Apps vs. Web Apps: and the Winner is …

Are web apps better than native apps, or vice versa?

There’s an ongoing debate about web apps vs. native apps. Some point to native apps’ natural speed, given that they don’t need to go through a browser. Others point out that web apps update faster, are more universal and easier to use.

With HTML, CSS and JavaScript, web apps’ barriers to entry are lower than Java- and Swift-based development. But Java and Swift come with many interactions that, so far, takes extra effort in JavaScript. Web apps require a working internet connection. Native apps require certain operating systems. A web apps can be responsive. A native app can fit its screen perfectly.

The pros and cons go on, but one thing’s clear: neither is going to overtake the other. And that’s good.

User Experience vs. User Experience

The principles of design apply to both types of app in slightly different ways because, in the end, we’re designing experiences for users. But there are some differences. For example, gestures are more common on native apps than websites (except for scrolling down long pages). Native app designers are more likely to use swipes than taps between screens, which — when done well — respond as if they were physical objects, following fingers like real paper.

That’s not to say web apps are devoid of gestures. Drag-and-drop has been available to front-end designers even before jQuery UI came around. But there’s a time and place for each types’ capabilities. For a start:

Web apps

Work on most any device (with a little responsive design planning)
The only “installation” required is to load a URL
Update to the latest version upon each page load
Are easily discovered with a quick web search
Are generally better suited to consuming data

Native apps

Take full advantage of native gestures like inertial scrolling, a.k.a. Rubberbanding
Don’t need to be downloaded every time they’re launched
Are (usually) guaranteed spam-free by app stores’ vetting process
Have easy access to accelerometers, cameras, GPS, and other device features
Can share data like contact info and photos with other apps
Have guaranteed one-tap icons on mobile devices’ home screens
Are generally better suited to letting users interact with data

But there are some overlaps, especially in design. Both require designers to consider personas and user flows. Both require smart use of color, typography and layout. And both benefit from prototyping processes. Design sensibilities aside, weighing the tradeoffs will shape the final product. For example, our own UXPin is a web app for many reasons. Our collaboration features work quicker on the web than it would on isolated mobile devices. We’ve also found that it’s much faster and easier to issue critical updates to our customers. Both let our users work from any computer with a ’net connection, save changes automatically, and review team members’ feedback on the fly — features we’ve found critical for success.

Crafting experiences

Which is better? Frankly, users don’t care that much. They use an app of any variety to get information or accomplish a task, regardless of how it’s created or accessed.

Likewise, UX designers can still apply the same principles to both types of apps. An interface still needs clarity and utility. Google’s Material design principles work great in any context, and collaboration is about teamwork, not platform preferences.

But web apps persist because of their unique properties. Native and web — which one wins? Both. There’s a time and place for each because, in the end, we’re designing for people, not platforms.Join us next week for another #uxpinchat!

From the #UXPinChat

@uxpin A1 I think web will be more popular for certain sectors and less in others… Native is always best for gaming for example #uxpinchat

— Michelle Matthews (@michematthews) April 15, 2016

@uxpin A1 Plus native feels more secure than web for financial apps, but again, as browsers improve that may change #uxpinchat

— Michelle Matthews (@michematthews) April 15, 2016

#uxpinchat I prefer #web-apps if I am not accessing the hardware functions. It can always be put into an native wrapper.

— #HashTagDeals (@hashtagdeals) April 15, 2016

@uxpin non-answer: not sure it matters bc both have their role in efficiency & usability. real answer: prob not — see: capitalism #uxpinchat

— Mike Donovan (@MikeLikeBike) April 15, 2016

@ryantriddle @uxpin Totally. But some tools, maybe not. Think of the prototyping tools that are web-based. #uxpinchat

— Michelle Matthews (@michematthews) April 15, 2016

A1 hard to say, depends on the product… Native offers so much options, but the web "seems easier" #uxpinchat https://t.co/wcfYV9SADS

— Steve Amara (@amarast) April 15, 2016

———————

@uxpin A2 Ability to move seamlessly from device to device, ease of sharing and collaborating #uxpinchat

— Michelle Matthews (@michematthews) April 15, 2016

@uxpin A2 cont. Some native apps can accomplish that too, but I find it's more front of mind when designing a web app #uxpinchat

— Michelle Matthews (@michematthews) April 15, 2016

@uxpin Simplicity in access. I can go straight from search to your site, see content on the spot. Quick, easy. #uxpinchat

— IselianGaming (@IselianGaming) April 15, 2016

@uxpin Native app download = time investment, offer more options. Browser access = quick, follow KISS rule #uxpinchat

— IselianGaming (@IselianGaming) April 15, 2016

@uxpin Consistent & established UX regardless of platform, browser or device. Avoids split & specialized dev on multiple systems. #uxpinchat

— Mike Donovan (@MikeLikeBike) April 15, 2016

A2 distribution. And documentation easier to find #uxpinchat https://t.co/zxJNupZhan

— Steve Amara (@amarast) April 15, 2016

#uxpinchat A2 All users will always be on the same web app version, vs not everyone would update their native apps.

— Uppercut (@madebyuppercut) April 15, 2016

@ux_benjamin @imgur. If I find a cat picture, don't make me DL the app. But if I want an account, features, I'll DL the app #uxpinchat

— IselianGaming (@IselianGaming) April 15, 2016

@uxpin There is no lengthy approvals process in comparison with native app stores meaning you can enhance an experience instantly #uxpinchat

— Matt Pointon (@matthewpointon) April 15, 2016

—————

@uxpin Features, features, features. Accounts, options, personalization, deep use. More control in your app vs browser. Security? #uxpinchat

— IselianGaming (@IselianGaming) April 15, 2016

A3 @uxpin SaaS web apps provide easier access to data and "sharebality" than any classic software. #uxpinchat

— Marcin Treder (@marcintreder) April 15, 2016

@uxpin A3 (Presumably) more secure & more powerful #uxpinchat

— Michelle Matthews (@michematthews) April 15, 2016

A3 you can really tailor the experience to each individual case/user. Personalisation! #uxpinchat https://t.co/kNnJrxxIam

— Steve Amara (@amarast) April 15, 2016

@uxpin finer & explicit control of UX ecosystem albeit at a dev cost. better integration w/ hardware/devices, i.e., notifications #uxpinchat

— Mike Donovan (@MikeLikeBike) April 15, 2016

#uxpinchat A3 Integration with devices, performance, offline mode.

— Uppercut (@madebyuppercut) April 15, 2016

——————-

A4 Yes there is! Native design has different expectations and UI constraints than a web app #uxpinchat

— Zachariah Reiner (@zsr5) April 15, 2016

@uxpin 100% yes, difference in what is offered. Intro content on web, deep on native, adjust UI accordingly. #uxpinchat

— IselianGaming (@IselianGaming) April 15, 2016

@uxpin A4 #uxpinchat I can only speak to mobile, but absolutely. Web has a lot more variables in terms of browsers, but with native you 1/2

— Michelle Matthews (@michematthews) April 15, 2016

@uxpin A4 …pretty much know the UI you're competing with #uxpinchat 2/2

— Michelle Matthews (@michematthews) April 15, 2016

A4 I have to thank Google for Material Design here. They really “unified” Web & Native UI design with it #uxpinchat https://t.co/HZbpx4J8tI

— Steve Amara (@amarast) April 15, 2016

A4 That being said, Web UI Design seems more uniform, hence easier to me. Native can quickly be challenging… IMHO #uxpinchat

— Steve Amara (@amarast) April 15, 2016

@uxpin certainly each have their own constraints. but the goal is for users to not feel/notice the burden of different platforms #uxpinchat

— Mike Donovan (@MikeLikeBike) April 15, 2016

A1 @uxpin access to web apps is so much easier than to software. Culture of access distribution must take over the world. #uxpinchat

— Marcin Treder (@marcintreder) April 15, 2016

@uxpin also, you can leverage established/familiar UI/UX patterns specific to each platform but still align w/ your universal UX. #uxpinchat

— Mike Donovan (@MikeLikeBike) April 15, 2016

—————-

@uxpin ha lighter fare. all the consistent UX ones: @chrome @amazon @twitter @Dropbox @feedly @newsifyapp @SlackHQ @netflix #uxpinchat

— Mike Donovan (@MikeLikeBike) April 15, 2016

A5 @uxpin Most of my work is done in native apps (until they are inevitably web based that is ^__^) so yeah, those. #uxpinchat

— Michelle Matthews (@michematthews) April 15, 2016

@uxpin In all seriousness, @Spotify, @gmail, @Twitch, @amazon for sure. Find myself using a LOT of Firefox/Chrome on the phone. #uxpinchat

— Michael Gremillion (@IselianGaming) April 15, 2016

@uxpin I love a bunch of web OR native apps too, but boy am I disappointed when I have to feel the difference b/n the two #uxpinchat

— Mike Donovan (@MikeLikeBike) April 15, 2016

Q5 @uxpin Tbh, there's no app I can't live without. Skype, now it's Slack. Omnigraffle, now Sketch. #ontothenextone #uxpinchat

— Michelle Matthews (@michematthews) April 15, 2016

The post Native Apps vs. Web Apps: and the Winner is … appeared first on Studio by UXPin.