- From: Marcos Caceres <w3c@marcosc.com>
- Date: Wed, 13 Mar 2013 15:18:14 +0000
- To: Tobie Langel <tobie@w3.org>
- Cc: Robin Berjon <robin@w3.org>, "Appelquist Daniel (UK)" <Daniel.Appelquist@telefonica.com>, "public-closingthegap@w3.org" <public-closingthegap@w3.org>
On 13/03/2013, at 2:35 PM, Tobie Langel <tobie@w3.org> wrote: > On Wednesday, March 13, 2013 at 2:36 PM, Robin Berjon wrote: >> On 13/03/2013 14:22 , Tobie Langel wrote: >>> On Wednesday, March 13, 2013 at 2:14 PM, Appelquist Daniel (UK) wrote: >>>> Actually your example underscores my point >>>> - because part of the expected experience of the Web is now being able to >>>> type search terms into some place on the browser chrome (increasingly the >>>> same place you type addresses) and having search results come up. >>> >>> >>> >>> Yes. Yet what if this functionality simply shifted to the OS level? >> >> Users can't tell the difference between something like this at the OS >> level or at the browser level. It's "on the computer". > > Precisely my point. > > If OS search has web search built-in, then the OS is the browser. Maybe. It would need to match apps, urls, and perform search... In a way that does not overload the user. I think this is what Android 2.x tried to do, but for me at least, it didn't feel like a good user experience.
Received on Wednesday, 13 March 2013 15:18:48 UTC