A business owner does not spend a significant part of their day at a desk. Opportunities to review figures are limited amidst customer visits, branch tours, and travel.
In this case, control is left until returning to the office in the evening or until the next day. An issue that could have been intervened during the day is only noticed afterward.
In this article, we explained which questions a mobile dashboard answers, which indicators are suitable for mobile, and the notification setup.
Table of Contents
Mobile and desktop difference
A mobile dashboard is not a scaled-down version of a desktop screen and should not be designed as such.
The usage context is completely different; the user is standing, on the go, or between meetings.
The viewing duration is very short; it is usually a check lasting a few seconds.
Therefore, a mobile screen should contain fewer indicators and larger numbers.
We discussed the desktop layout in the dashboard customization article.
Mobile-friendly indicators
Indicators to be included on the mobile screen should be of a type that can be expressed with a single number.
Daily turnover, total collections, and the number of open orders fit this definition and can be read quickly.
Complex tables and multi-dimensional charts, however, are unreadable on mobile; these should remain on the desktop.
Warning counts are also suitable for mobile; how many critical stocks or delayed orders exist can be seen at a glance.
Comparison data should also be added; the difference between the number and yesterday or last week defines the meaning.
Screen design
The initial view of the mobile screen should contain the three or four most critical indicators.
Sections requiring scrolling are, in practice, areas that are looked at much less frequently.
Numbers must be large and legible; small text cannot be read while on the move.
The use of color must also carry meaning; normal situations and those requiring attention must be distinguishable.
Fast loading of the screen is the most critical design criterion; a screen that opens slowly is never opened.
Notification link
The strongest aspect of mobile usage is that the information can find the user.
Sending notifications in critical situations allows intervention without waiting for the screen to be opened.
The number of notifications should be kept very limited; frequent notifications lead to the app being closed shortly.
Only situations that genuinely require action should generate notifications.
Notification management notification management we covered in the article.
Quick actions
Seeing is not enough on mobile; certain actions need to be performable from there.
Approval processes are the best example of this; approving a pending request takes a few seconds.
This prevents processes waiting for approval from being delayed unnecessarily and speeds up operations.
Complex data entries are not suitable for mobile; these should be done on the desktop.
The right distinction is to use mobile for control and approval, and desktop for production.
Link behavior
Connection quality may not always be good during mobile use, and the screen must be prepared for this.
In case of a slow connection, showing the last known values is preferred instead of the screen remaining completely blank.
In this case, the time of the data should be clearly stated; old data should not be mistaken for current data.
Keeping the amount of data low is also important in mobile use; heavy screens are both slow and costly.
Offline scope should be evaluated during the setup phase according to needs.
Mobile security
Mobile devices can be lost or stolen; this is a risk that does not exist on the desktop.
Device lock and additional authentication at the application level significantly reduce this risk.
Session duration can also be kept shorter on mobile; a session that remains open for a long time is risky.
It is also important that the session can be terminated remotely in case of loss.
Whether sensitive indicators should be displayed on mobile or not should also be evaluated separately.
Use cases
The value of a mobile dashboard is seen more clearly in concrete scenarios.
During a branch visit, a manager can view that branch's daily figures before entering and go prepared.
Before a customer meeting, the current balance and open order information can be quickly checked.
Pending approvals can be completed during travel, and operations do not wait.
A quick check over the weekend is also possible; the situation can be seen without going to the office.
Limitations
A mobile dashboard does not meet every need, and realistic expectations must be set.
Detailed analysis and comparative reports require a desktop; a small screen is not suitable for this task.
Bulk data entry and correction operations cannot be performed efficiently on mobile either.
Mobile scope may also vary on a module basis; this scope should be clarified before setup.
The right approach is to position mobile as a complement to the desktop, not a replacement.
Points to consider
Porting a desktop screen directly to mobile is the most common design mistake.
Sending excessive notifications also leads to the app being closed.
Failing to specify the timestamp of the data increases the risk of making wrong decisions.
Neglecting security measures creates a serious risk in case of device loss.
Indicators are defined in the dashboard module and reflected on mobile.
Frequently asked questions
Which indicators are visible on mobile?
Summary indicators that can be expressed with a single number are suitable; we determine the scope according to your needs.
Does it work offline?
We evaluate the scope according to your scenario; we clarify the connectivity requirement before setup.
Can approval processes be done from mobile?
Yes, approval workflows are among the operations best suited for mobile use.
Is a separate application required?
You log in to the mobile interface with the same account; you can check the single session article.
The mobile dashboard gives managers who are not at their desks the opportunity to intervene during the day. Its value is directly proportional to the simplicity of the screen.
Do not just copy the desktop screen as is; design a separate and much shorter set for mobile.
Put only three or four indicators in the initial view; sections requiring scrolling are looked at very little in practice.
Keep notifications very limited as well; apps that send frequent notifications are muted in a short time.
Move approval processes to mobile; processes that stall due to pending approvals are accelerated with this single step.
Be sure to show the timestamp of the data as well; an old value displayed on a weak connection produces wrong decisions when thought to be current.
Handle mobile security separately too; device loss is a risk that has no equivalent on the desktop, and session duration should be adjusted accordingly.
Finally, keep expectations realistic; mobile is the place for quick control and approval, not detailed analysis.
by consulting with the EQLEM team, you can clarify your mobile usage scope.