Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

How to Set Your Mobile App Strategy for 2017

DZone's Guide to

How to Set Your Mobile App Strategy for 2017

If your company writes great single-purpose mobile apps this year, you’ll have taken a major first step towards a cohesive enterprise mobile app strategy for 2017.

· Mobile Zone
Free Resource

Discover how to focus on operators for Reactive Programming and how they are essential to react to data in your application.  Brought to you in partnership with Wakanda

This year will prove to be a pivotal one for enterprise mobility. It’s a year in which companies will turn away from thinking of mobile development as targeting only applications or websites and instead become central to everything an enterprise does. Here are some insights and ideas for developing your own mobile app strategy for 2017.

In his blog titled Big Things Ahead for Mobile App Strategies in 2017Gartner Research Director Jason Wong notes:

“Mobile apps are not shiny, new toys anymore. They are a must-have technology for any business looking to compete for customers and elevate its workforce. Previously a separate and isolated concern, mobility is becoming an embedded part of every application and digital product.”

That means enterprises need to think of mobility as a continuum across the entire company and should not focus all their mobile efforts towards building apps. He says:

“Mobile apps are only the beginning of a journey into the post-app era, where user experiences are continuous, ambient and omnichannel — beyond phones and tablets, and across the digital landscape.”

Advice for Building Your Next Mobile App

That’s a lot to bite off at once, of course, and Wong knows it. So, he recommends a straightforward first mobile app strategy step: Develop the right competencies and strategies for building mobile apps, and then take what’s learned from doing that and incorporate it throughout the rest of the enterprise.

If you can accomplish that this year, you’ll have gone a long way towards a cohesive enterprise mobile app strategy for 2017. But you’ll need to keep in mind that developing apps is very different than writing traditional applications. And if you’re looking for advice on how to do it, you can’t do better than Gartner’s advice in its report, The App and Its Impact on Software Design.

Gartner’s big takeaway: Mobile apps should be designed very differently from traditional desktop software. In traditional desktop software, the report notes, there’s often a “kitchen-sink” approach: Throw in every feature and capability anyone might need. Unfortunately, many developers think of mobile apps merely as “miniature versions of applications,” in the words of the report.

That’s the wrong approach for writing mobile apps. Instead, the report says, the value of mobile apps comes from “the ability to do one thing very well. Apps are about purposefulness. Features become a means to that end, rather than the end themselves.”

So, Gartner recommends that developers consciously constrain their apps to do one primary thing, and do that well. Once that is accomplished, businesses should use the same general design principles for integrating mobility capabilities throughout the rest of the enterprise. So, if your company writes great single-purpose mobile apps this year, you’ll have taken a major first step towards a cohesive enterprise mobile app strategy for 2017.

Learn how divergent branches can appear in your repository and how to better understand why they are called “branches".  Brought to you in partnership with Wakanda

Topics:
mobile ,app development ,mobile app strategy ,single purpose apps

Published at DZone with permission of Amy Groden-Morrison, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}