- 101 UX Principles
- Will Grant
- 191字
- 2021-07-16 18:02:38
Chapter #11. Search Should be a Text Field with a Button Labeled "Search"
Search has, over the years, been over-designed. One common anti-pattern is hiding search behind a control to activate it. Slowing the user down and adding an extra step might remove an input field from your view but at the expense of familiarity.
If you're offering your users a search function, then show them a text field with a search button. If you're using an icon, then use a "magnifying glass" icon. This is the archetype and using anything else makes no sense anymore.

The "gold standard"
On a mobile phone screen, there may not be enough space to always show the search field, but I'd still encourage you to evaluate if you can. Tucking the search field into the top of a scrolling view can work well:

Search at the top of a list view only appears when "pulled down"
Bonus points: when the user taps the Search tab in a mobile app, show the search view, move the cursor to the search field and show the device keyboard for them.
- Windows phone 7.5 application development with F#
- Instant uTorrent
- Linux KVM虛擬化架構實戰指南
- 深入淺出SSD:固態存儲核心技術、原理與實戰
- The Applied AI and Natural Language Processing Workshop
- Mastering Manga Studio 5
- 基于Apache Kylin構建大數據分析平臺
- Rapid BeagleBoard Prototyping with MATLAB and Simulink
- Managing Data and Media in Microsoft Silverlight 4:A mashup of chapters from Packt's bestselling Silverlight books
- FL Studio Cookbook
- 電腦橫機使用與維修
- 嵌入式系統原理及應用:基于ARM Cortex-M4體系結構
- 可編程邏輯器件項目開發設計
- 微服務實戰
- UML精粹:標準對象建模語言簡明指南(第3版)