Look for the 🛠emoji if you’d like to skim through the content while focusing on the build and execution steps. These situations need a way to insert a step into the login process to present the announcement to the user.
This is especially true if your application has different versions for different platforms, requiring you to make changes in multiple codebases.
When surprises like these appear, you shouldn’t make changes to your application just to display an announcement. This includes things that are hard to predict, such as unscheduled downtime. While you can predict some of these announcements (e.g., informing the user that their account is about to expire or is running out of storage space or some other resource), many situations that need these announcements will arise with little or no warning. The announcement is important enough to interrupt the usual Login flow with a separate page or screen that requires the user to activate a button, link, or other user interface control before proceeding to the application. Every system administrator’s worst nightmare: an outage.Notifications about the user’s account, such as an approaching expiry date or that they are running out of storage space allotted to their account.Changes to the application that will affect its functionality or the user experience.Upcoming maintenance, during which time the application will be unavailable.Sooner or later, your application will need to present the user with an important announcement immediately after logging in.
0 kommentar(er)
