Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Interface bloat

From Wikipedia, the free encyclopedia
This article has multiple issues. Please helpimprove it or discuss these issues on thetalk page.(Learn how and when to remove these messages)
This articleprovides insufficient context for those unfamiliar with the subject. Please helpimprove the article byproviding more context for the reader.(April 2016) (Learn how and when to remove this message)
This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Interface bloat" – news ·newspapers ·books ·scholar ·JSTOR
(September 2024) (Learn how and when to remove this message)
This articlepossibly containsoriginal research. Pleaseimprove it byverifying the claims made and addinginline citations. Statements consisting only of original research should be removed.(November 2024) (Learn how and when to remove this message)
(Learn how and when to remove this message)
Overload of elements on an interface
An image depicting three red buttons of importance, clustered with tertiary or otherwise unnecessary buttons.
An example of interface bloat

Interface bloat is a phenomenon insoftware design where aninterface incorporates too many (often unnecessary) operations or elements, causing issues such as difficulty navigating and usability.[1][2]

Definition

[edit]

While the termbloat can refer to a variety of terms in software design,[3] Interface bloat refers to the phenomenon where the user interface (UI) becomes unnecessarily complex and overloaded with features, options, or elements that can overwhelm users.[4] This often leads to a cluttered experience, decreased usability, and increased difficulty for users to accomplish their tasks efficiently.[1][2] Interface bloat can arise from various sources, including the addition of excessive functionality without proper consideration of user needs, the merging of disparate features, or pressure to include numerous options to cater to a broader audience.[2]

References

[edit]
  1. ^ab"Do Computers Have to Be Hard to Use?".archive.nytimes.com. Retrieved2024-11-09.
  2. ^abcAkiki, Pierre; Bandara, Arosha; and Yu, Yijun (24–27 June 2013). "The Open University's repository of research publications regarding minimizing the bloat in enterprise applications Conference Item".Fifth ACM SIGCHI Symposium on Engineering Interactive Computing Systems. London, UK.S2CID 2935087.
  3. ^Kaufman, Leah; Weed, Brad (1998-04-01)."Too much of a good thing?: Identifying and resolving bloat in the user interface".CHI 98 Conference Summary on Human Factors in Computing Systems. CHI '98. New York, NY, USA: Association for Computing Machinery. pp. 207–208.doi:10.1145/286498.286693.ISBN 978-1-58113-028-7.
  4. ^McGrenere, Joanna; Moore, Gale (15–17 April 2000).Graphics Interface. Montréal, Québec, Canada: Canadian Human-Computer Communications Society. pp. 187–196.ISBN 0-9695338-9-6. Retrieved9 November 2024.
Stub icon

Thissoftware-engineering-related article is astub. You can help Wikipedia byexpanding it.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Interface_bloat&oldid=1262004934"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2025 Movatter.jp