Application Development Blog Posts
Learn and share on deeper, cross technology development topics such as integration and connectivity, automation, cloud extensibility, developing at scale, and security.
cancel
Showing results for 
Search instead for 
Did you mean: 

In general, business projects often need multi-users to deal with their daily work. For example, the users involved may include sales consultant, area manager, market operation manager, customer service, etc. Different types of business determine that different users focus on different work contents in a CRM system. With the convenience brought by the current mobile devices, our customer often require that the design layout can handle the problem of how to log in to the app and how to view the work content while multi-users were configured in this system.


For example:


1. How to design when different users contain totally different jobs?


2. How to design a super administrator who has all permissions when a person contains multi-users?


3. How to design when different users contain part of the same work and other different work modules?


I try to list these users and their main work to express my design concept via mockup.


Case 1: How to design when different users contain totally different jobs?




After the data collection and analysis in the early stage, it is assumed that user A is mainly responsible for (Section 1, 2, 3), user B is mainly responsible for (Section 4, 5), and user C is mainly responsible for (Section 6, 7, 8). If they belong to different jobs in most cases, the overlap is very small, so the following design layout is recommended. After the user logs in to the app, he / she directly enters the corresponding interface to see different content through the change of tab bar. The design layout is only for the case that the number of main work is not complex.

Case 2 How to design a super administrator who has all permissions when a person contains multi-users?



For example, user A may have the permission to add, delete, and modify, user B may have read-only permission, and user C may be other work content. User D, on the other hand, may be a super administrator , who has operational privileges for all users. In this case, if a person has multi-user permissions in the background, it is recommended to click a user and jump to the corresponding interface.


It is worth emphasizing that user D, as a super administrator, should be able to do everyone's work independently. It is not recommended to operate on the app. It is encouraged to operate on PC. If it is forced to operate on the app, the interface content will be messy.


The official guideline for iOS tab bar can only contain 5 sections or less.


Case 3:  How to design when different users contain part of the same work and other different work modules?



For this situation, fixed tab bar can bring stability feelings while different users enter the app, and the difference of content viewed can be felt by controlling the content in the last icon (more). The advantage of this layout is that users who log in to the app will not feel strange due to the change of the bottom bar, and only click more to find more different work.


The disadvantage is that the relevant functions are collapsed, resulting in low priority except for fixed functions.


Conclusion: in recent years, due to more and more business demands, mobile APP design framework is required to be flexible and easy to use. We hope to help people "happily" and "easily" complete their daily work, rather than "have to" use application.


If you have any additional doubts about  multi-user mobile application? you can comment it below. ?


 

 

 

 

 

 

 

 

 

 

 

 
1 Comment