News for hackers. Stuff that matters.
Re:Ask HN: Only one text field allowed on the webapp by prodigal_erik on Sunday July 11, 2010 @07:34PM (#1506371)
If you have more than one feature and only one field, you will inevitably end up with conventions for smuggling extra data into it, which users will then have to learn. E.g., Twitter has @user and #tag, and Google has site:, inurl:, and cache:.
Re:Ask HN: Only one text field allowed on the webapp by rabidsnail on Sunday July 11, 2010 @08:18PM (#1506421)
This way we can have our cake and eat it too. New users see only one input, making it very clear what they're supposed to do, and advanced users can still do advanced things.
Re:Ask HN: Only one text field allowed on the webapp by danhak on Sunday July 11, 2010 @09:10PM (#1506483)
Might be worth noting that @user and #tag were conventions invented by users and later adopted by Twitter itself
Re:Ask HN: Only one text field allowed on the webapp by petervandijck on Monday July 12, 2010 @03:19AM (#1507098)
Chrome has 1 textfield that's both used for search and for urls.

Related: I've found the search textfield in the Windows 7 START menu hugely useful. Just type 2 or 3 letters instead of browsing through folders of programs. 1 textfield + autocomplete = powerful for known-item searching.

And: Twitterbar adds more functionality (tweet) to the URL bar of Firefox.

One textbar is definitely the way to go, with as only downside that learnability goes down a little :)