Topic
Human interface guidelines
About: Human interface guidelines is a research topic. Over the lifetime, 76 publications have been published within this topic receiving 900 citations. The topic is also known as: HIG & user interface guidelines.
Papers published on a yearly basis
Papers
TL;DR: This study aims to evaluate compliance with Android and Apple guidelines on design and usability by assessing the usability recommendations of a set of 24 selected mobile PHR applications and will help both PHR users to select user-friendly mobile PHRs and providers and developers to identify the good usability practices implemented by the applications with the highest scores.
Abstract: Mobile Personal Health Records (PHRs) have achieved a particularly strong market share since the appearance of more powerful mobile devices and popular worldwide mobile application markets such as Apple's App Store and Android's Google Play. However, Android and Apple have a set of recommendations on design and usability targeted towards developers who wish to publish apps in their stores: Android Design Guidelines and iOS Human Interface Guidelines. This paper aims to evaluate compliance with these guidelines by assessing the usability recommendations of a set of 24 selected mobile PHR applications. An analysis process based on a well-known Systematic Literature Review (SLR) protocol was used. The results show that the 24 mobile PHR applications studied are not suitably structured. 46 % of these applications do not use any of the recommended patterns, using instead lists or springboards, which are deprecated patterns for top-level menus. 70 % of the PHRs require a registration to be able to test the application when these interactions should be delayed. Our study will help both PHR users to select user-friendly mobile PHRs and PHR providers and developers to identify the good usability practices implemented by the applications with the highest scores.
73 citations
1 Jun 1992
TL;DR: A knowledge-based tool is presented, containing design knowledge drawn from general guideline documents and toolkit-specific style guides, capable of evaluating a user interface design produced in a UIMS, showing that part of what the designers consider relevant design knowledge is related to the user's tasks and thus cannot be applied to the static design representation of the UIMs.
Abstract: The motivation for our work is that even though user interface guidelines and style guides contain much useful knowledge, they are hard for user interface designers to use. We want to investigate ways of bringing the human factors knowledge closer to the design process, thus making it more accesible to designers. To this end, we present a knowledge-based tool, containing design knowledge drawn from general guideline documents and toolkit-specific style guides, capable of evaluating a user interface design produced in a UIMS. Our assessment shows that part of what the designers consider relevant design knowledge is related to the user's tasks and thus cannot be applied to the static design representation of the UIMS. The final section of the paper discusses ways of using this task-related knowledge.
72 citations
1 Jan 2011
TL;DR: The purpose is to improve older users’ potential in using information technologies, and topotentially allow older users to gain more benefit from using of computer software.
Abstract: In the world today, the portion of aging people grows continuously. Due to successfulof healthcare services, people are living longer and the number of newborn isdecreasing. This can imply that the ...
56 citations
5 Apr 2003
TL;DR: A multi-leveled framework for user interface design guidelines of Web applications is presented, dubbed the 'Bull's-Eye' due to its five layers, represented as concentric circles, which provides a bridge between the two extremes.
Abstract: A multi-leveled framework for user interface design guidelines of Web applications is presented. User interface design guidelines tend to provide information that is either too general, so that it is difficult to apply to a specific case, or too specific, so that a wide range of products is not supported. The framework presented is unique in that it provides a bridge between the two extremes. It has been dubbed the 'Bull's-Eye' due to its five layers, represented as concentric circles. The center of the Bull's-Eye is the Component layer, followed by Page Templates, Page Flows, Interface Models and Patterns, and Overarching Features and Principles. To support this approach, requirements were gathered from user interface designers, product managers, UI developers, and product developers. Also, usability testing of the guidelines occurred on several levels, from broad guideline tests to more specific product tests. The guidelines and lessons learned are intended to serve as examples for others seeking to design families of Web applications or Web sites.
53 citations
Patent•
IBM1
TL;DR: In this article, the look and feel of the OS/2 operating system is added to the Swing application program interface (API) in an enhanced version of the API, referred to herein as AWTSwing.
Abstract: A system and method are disclosed whereby the look and feel of the OS/2 operating system is added to the Swing application program interface (API), in an enhanced version of the API, referred to herein as AWTSwing. A further disclosure is the creation of a thread-relative setLookAndFeel method, which only accepts calls from a particular thread to adopt a prescribed look and feel. This makes it possible for an application to have a look and feel distinct from that of the platform, or of other concurrently executing applications. This capability is not present in the conventional version of the Swing API, which treats look and feel settings as global.
32 citations
Related Topics (5)
Performance Metrics
| Year | Papers |
|---|---|
| 2021 | 1 |
| 2020 | 2 |
| 2019 | 3 |
| 2018 | 2 |
| 2017 | 1 |
| 2016 | 3 |