Last Update: Dec 08, 2022
Platform: Mobile
Designer: Rebecca Florence Bijjiga
_SF FN Homepage
SF Home Collapsed Header
Intro
Information on the home page is considered to be completely dynamic and personalised to the user, driven by user and business context, user profile, time of login (in the day, week, month or year), user behaviour/usage patterns, etc.
Content on the home screen is classified into following types : Navigation, Conversational Assistant, Approvals, Quick Action, Engagement Cards, Organizational Cards.
Usage
Quick actions are light weight functionalities that users need on a frequent basis. They are light-weight and consists of 3 to 6 fields with an explicit primary action such as submit, save or send. They are frequent actions that has to be recurring within one year.
- Its valuable to our customers and end-users.
- Its a simple and recurring task that the users can complete quickly without navigating away from homepage.
- Users come to this quick action with a primary purpose in mind
- It represents 80% of the use cases. It's a use case that majority of the users in your product area do.
- You want to create a quick access to a module functionality
- The task requires a lot of time and a lot of thinking
Types
At any given time, there would be 8 Quick Actions Tiles for the user and only ONE tile can be opened/accessed at a time, these will be static and will remain the same for all users. These quick actions from various modules are based on recommendations from the system and intended to work like mini-apps. but clicking on them will only open an instance (modal dialog) of the task within the homepage layer, without navigating away from the app or opening a pillar page. There are two tiles default provided to all the users : Reminders and Favourites
Structure & Components
Behavior & Interaction
Quick actions intend to allow users to perform a quick task without navigating away from homepage.
The task should be single-focused and with minimum number of interactions. Tasks that with more complexity and multiple levels of interactions should not be a choice for quick actions.
When design for quick actions iOS, make the design simple and quick. Please avoid the following:
- More than 1 level depth of drill in on a component level in a standard full screen modal.
- Triggering another modal or jump out of the modal in order to finish the task. For example, an action button placed within the modal to trigger another modal.
Responsiveness & Adaptiveness
Application-specific examples
In Time Management, a dedicated quick action was designed on iOS following the guidelines to help the employees to clock in and clock out on a daily basis from the home page.
The same dedicated quick action was designed on Android following the guidelines to help the employees to clock in and clock out on a daily basis from the home page.
Accessibility
Both screen flows for iOS and Android are based on standard controls. The scenarios have passed the A11Y review checks and without any accessibility issues.
Resources