According to the Notifications design pattern, notifications should not be used for information that is currently available on-screen, technical operations that don’t need user involvement, or errors that can be resolved without the user (UI Patterns, n.d.).

UI design patterns are used to seeped up the design process and thus save money (Interaction Design Foundation, n.d.). UI design patterns are proven designs that can be applied to similar situations (Interaction Design Foundation, n.d.). For example, user registration designs that have been shown to work can be simplified and applied to other UIs.An Account Registration UI design pattern like the one shown in 10 UI Design Patterns You Should Be Paying Attention To requires the user to only fill in a minimum amount of information. Using a design for registration that only requires a user to fill out the minimum amount of information, like email and password increases the likely hood that they will sing up. Furthermore, in the Account Registration UI pattern, it is suggested that the benefits of signing up are highlighted to further encourage the user to sign up. The account registration pattern solves three problems according to (Jovanovic, 2009):User needs to register to access the content.User needs personalized content.The user needs to re-enter data.The account registration design pattern can be applied to the Alfred! project by minimizing the amount of data that the user needs to enter at sign up. For example, the Alfred! app is used to monitor thermostats and other smart devices and the information to allow the app to monitor theses devices will eventually need to be entered; however, the user does not need to enter this information at sign up. The Alfred! app could just require the user to enter their name, email, and a password at sign up. Another solution would be to use the option of letting a user sign up with Apple ID.Another UI design pattern that would be useful for the Alfred! app is the Notifications Design Pattern. The notifications design pattern is used to get the user’s attention for important information or time-sensitive information (UI Patterns, n.d.). According to the Notifications design pattern, notifications should not be used for information that is currently available on-screen, technical operations that don’t need user involvement, or errors that can be resolved without the user (UI Patterns, n.d.). The Notifications Design Pattern can be used in the Alfred! app to inform the user of important information such as if the app is unable to connect to their smart thermostat.The Frequently Asked Questions (FAQ) Design Pattern form UI Patterns would also be useful for the Alfred! app. The FAQ Design Pattern is implemented by gathering the most asked user support questions and placing them in an easy to search area on a site or in an app (Patterns, n.d.). The FAQ Design Pattern can be used in the Alfred! system to design a system to answer some of the most asked customer support questions.