The number of people using their mobile to access information is steadily and rapidly increasing. Two years ago already, 93% of all mobile users, accessed online information with their mobile.

Of course, not all of them want to access your corporate KPI solution. However, it shows the increasing relevance to provide KPI dashboards in a seamless way on mobiles too.

I’ve already published a post about why I think mobile-first is the strategy to follow when setting-up KPI dashboards or solutions.

This article now summarizes 5 best-practices which are often overlooked — but you should definitely follow when setting up a KPI dashboard or KPI solutions for mobiles.

Get rid of your navigation bar or menu

Space matters, especially on mobiles. Mobiles are flats in the centre of a vibrant city. Rents are super-high and every pixel is expensive.

That’s why there’s no money or no space to waste with a constant menu or navigation bar.

And we need that space for other more important content.

It’s much better to rely on so called hamburger menus. A small menu button at the top of your solution, which expands whenever needed.

Here’s a good example from Wikipedia’s mobile solution:

Probably, it’s even possible to avoid a menu completely and introduce an alternative navigation functionality (that’s what we do with our KPI apps).

Functions & Clickable Areas in reach

How often do you use your mobile? I guess very often.

When waiting for the bus in the morning, while having the first coffee and of course in boring meetings. Maybe your reading this blog post on your mobile right now.

But much more important: How do you use your mobile? 75% sure, you’re using your thumb to navigate.

What does that mean? In order to provide a seamless experience for your user, you have to place the clickable content in an area easy to reach with your thumbs:

https://www.smashingmagazine.com/2016/09/the-thumb-zone-designing-for-mobile-users/

Placing the clickable content in the green area will massively ease the use of your solution.

Reduce data size

True, KPI dashboards are based on a lot of graphics. However, data volume still matters when it comes to seamless and excited usage of your solutions.

In case your mobile solution receives images to display, you have to take care, to reduce the size of the images as much as possible.

Of course, you still want to provide a high-quality image.

What we do alternatively: Our KPI Apps only receive XML or JSON data and renders the KPIs within the app. Thus, we massively reduce the exchange data volume.

Responsive Design

This is so very important.

A solution, a KPI dashboard solution, which does not provide or support responsive design shouldn’t be rolled-out anymore.

5 Recommendation when it comes to responsiveness:

  1. If you have to use graphics provide a tailored graphics for mobile usage, small in size.
  2. Define the layout and order how your content should be displayed on smaller screens
  3. Think about animations — are they really required on mobiles? Are they working?
  4. Think about videos — are they really required?
  5. JavaScript is super-cool but does not always work on mobiles — at least as long your accessing your solution via browser. Think about developing a own app for your KPI solution.

Expandable Content

As mentioned, space is expensive. That’s why you should think about expandable content when designing your dashboard solution.

This helps to reduce the initial shown content and provides the freedom to your users if and when additional content is expanded.

In our KPI apps we usually cluster KPIs in groups which then can be expanded.

//www.id1.de/wp-content/uploads/2019/09/Iphone-X.png

More content needed?

Download our Airline Operations KPI Guide

The KPI Guide introduces 38 different KPIs. Each KPI is listed with a short description / explanation as well as an examples and specific notes.