Sergey Nivens - Fotolia
Mobile is not the same as desktop.
That's a no-brainer, right? But it's easier said than done when it comes to enterprise Windows and mobile applications. Development teams must consider the platform(s) an application will run on and the ramifications of those decisions. The features required before an app can be released may be different based on the platform. And the product manager may even have to maintain separate roadmaps for each operating system's version of the app.
Imagine you have a product roadmap that includes 100 features. You have done all of the required research, and you know what features need to be developed first to form the minimum viable product (MVP). In other words, you have a decent idea of what features should be included in release 1.
From here, the most important question to answer is: On which platform(s) will the app's audience (end-user employees, customers, etc.) use this application? The answer is critical in determining which features -- and how many of them -- you can present in the app's user interface.
80/20 rule reversal
I often use Microsoft Office as an example to illustrate the differences between Windows and mobile apps. Many of us have heard the statement that 80% of desktop Word users interact with only 20% of its features. This figure is a bit anecdotal, but the point is that Office's developers can afford to include a ton of features because they have the luxury of the desktop platform, which has a huge user interface. Windows desktops and laptops with large screens and external monitors allow for hundreds of features to be presented, and there is little concern if features are used or not.
If 80% of users of a desktop application utilize 20% of its features available, it is acceptable from a product management perspective. In mobile, however, this 80/20 rule is turned on its head. On smartphones and tablets, there is significantly less real estate in which to fit all possible features. If a user is not utilizing 80% of the features presented, there is considerable misuse of valuable space. And with that, users will uninstall the app as quickly as they installed it.
Going back to the scenario of having 100 potential features on the list, and based on the 80/20 rule, you could build 80 features into a desktop application with a low risk of negative user experience. But for a mobile version of the same app, including just 20 features would give you the same odds.
That is a major difference in the number of features to deploy to achieve the same likelihood of success. As such, the weighting of the importance of features to include in each version of the app requires serious discussion, research and user experience (UX) analysis.
UX analysis aids Windows and mobile development
UX analysis goes well beyond discussions and debates among the stakeholders investing in the development of an application. Developers must consider the effects of including certain features, based on the user's needs and the desired platforms.
As an example, a critical requirement in UX analysis is the creation of use cases and personas for your targeted end users. Based on real-life observations, surveys and focus groups used to create the personas, product developers can understand what features will compliment or disrupt the end users' experiences with the application. This valuable insight will aid in the decision-making process to determine which features to include in release 1.
To put all of this into perspective, let's turn back to the Office example. Even Microsoft's talented application development staff had to muscle through a steep learning curve on how best to launch Office in the mobile world. Think of all the features that we know and love in the desktop version. Developers had to determine which to include in the mobile versions, and then had to consider how best to deploy them. The developers could not cram in all of the valuable features desired by desktop users, and it took Microsoft the better part of 12 months from announcing mobile versions of Office to finally launching viable products.
It is a daunting task to figure out which features to include in applications, but the more thought and analysis you put into it, the better off you and your users will be.