- 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.
- 圖解西門子S7-200系列PLC入門
- Augmented Reality with Kinect
- Linux KVM虛擬化架構實戰指南
- 施耐德SoMachine控制器應用及編程指南
- INSTANT Wijmo Widgets How-to
- 計算機應用與維護基礎教程
- Unity 5.x Game Development Blueprints
- 電腦維護365問
- 單片機開發與典型工程項目實例詳解
- 微控制器的應用
- The Applied Artificial Intelligence Workshop
- Deep Learning with Keras
- Service Mesh微服務架構設計
- 微服務架構實戰:基于Spring Boot、Spring Cloud、Docker
- FPGA的人工智能之路:基于Intel FPGA開發的入門到實踐