<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Integrating Ubiquity into Firefox: UI Mockups</title>
	<atom:link href="http://blog.mozilla.com/faaborg/2009/03/25/integrating-ubiquity-into-firefox-ui-mockups/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.mozilla.com/faaborg/2009/03/25/integrating-ubiquity-into-firefox-ui-mockups/</link>
	<description>User Experience Design at Mozilla</description>
	<lastBuildDate>Sun, 12 Feb 2012 23:42:05 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: eg ge</title>
		<link>http://blog.mozilla.com/faaborg/2009/03/25/integrating-ubiquity-into-firefox-ui-mockups/comment-page-1/#comment-137531</link>
		<dc:creator>eg ge</dc:creator>
		<pubDate>Tue, 19 May 2009 22:05:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=82#comment-137531</guid>
		<description>I&#039;d find it really cool, if the map would link to the openstreetmap.org -project to make it more popular.</description>
		<content:encoded><![CDATA[<p>I&#8217;d find it really cool, if the map would link to the openstreetmap.org -project to make it more popular.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Mellor</title>
		<link>http://blog.mozilla.com/faaborg/2009/03/25/integrating-ubiquity-into-firefox-ui-mockups/comment-page-1/#comment-130759</link>
		<dc:creator>John Mellor</dc:creator>
		<pubDate>Thu, 09 Apr 2009 23:37:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=82#comment-130759</guid>
		<description>&quot;Idea 1: Command Bar + Action Button&quot; looks almost perfect! It finally gets rid of the redundant search bar, and combines the best of Google Chrome&#039;s search suggestions with Ubiquity&#039;s powerful commands while remaining very easy to learn (and non-power-users can still use the mouse if they prefer).

My only question is how you plan to integrate Awesomebar results (which are very useful). I would suggest that in the case where it is doing a Google search by default (but you haven&#039;t explicitly typed &quot;google&quot;) it should show both Awesomebar results and Google search suggestions. These could be one on top of the other, intermixed, or side by side, but it is important that once the user sees a result they like and clicks it there&#039;s no risk of a better-ranked result having loaded in its place, taking them to the wrong place.

Great stuff, keep it going!</description>
		<content:encoded><![CDATA[<p>&#8220;Idea 1: Command Bar + Action Button&#8221; looks almost perfect! It finally gets rid of the redundant search bar, and combines the best of Google Chrome&#8217;s search suggestions with Ubiquity&#8217;s powerful commands while remaining very easy to learn (and non-power-users can still use the mouse if they prefer).</p>
<p>My only question is how you plan to integrate Awesomebar results (which are very useful). I would suggest that in the case where it is doing a Google search by default (but you haven&#8217;t explicitly typed &#8220;google&#8221;) it should show both Awesomebar results and Google search suggestions. These could be one on top of the other, intermixed, or side by side, but it is important that once the user sees a result they like and clicks it there&#8217;s no risk of a better-ranked result having loaded in its place, taking them to the wrong place.</p>
<p>Great stuff, keep it going!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: D'Artagan</title>
		<link>http://blog.mozilla.com/faaborg/2009/03/25/integrating-ubiquity-into-firefox-ui-mockups/comment-page-1/#comment-128801</link>
		<dc:creator>D'Artagan</dc:creator>
		<pubDate>Thu, 02 Apr 2009 03:34:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=82#comment-128801</guid>
		<description>Most definitely I prefer the first option.  It is elegant in that it doesn&#039;t require learning another method and it keeps the browser real estate minimalist.  These coincide perfectly with your ideas of flow and content over browser, which I hugely agree with. The best thing about this interface is that normal users could stumble upon helpful commands by just trying to get information in the awesomebar.  For example: map &quot;address&quot;, currently brings up a Google page, with ubiquity like functionality it would cut out this middle search, giving users the impression of better functionality without them having to learn anything.  It is necessary though, for the Awesome bar to still maintain its original functionality of frecency and bringing up likely web pages.  I, and many users I know, have come to rely on this one stop search and find box.  TaskFox should improve upon it, but should not interrupt it.  Additionally, it would be nice to give the user an opportunity to discover more commands, possibly through the drop down that you have slotted, or by mixing them into the awesome bar results (though a system would have to be devised which would do this with discretion, not listing more than two or three).  Above all, in order to have a successful adoption and browser, remember that Taskfox is an extension of the awesomebar, not a new application.</description>
		<content:encoded><![CDATA[<p>Most definitely I prefer the first option.  It is elegant in that it doesn&#8217;t require learning another method and it keeps the browser real estate minimalist.  These coincide perfectly with your ideas of flow and content over browser, which I hugely agree with. The best thing about this interface is that normal users could stumble upon helpful commands by just trying to get information in the awesomebar.  For example: map &#8220;address&#8221;, currently brings up a Google page, with ubiquity like functionality it would cut out this middle search, giving users the impression of better functionality without them having to learn anything.  It is necessary though, for the Awesome bar to still maintain its original functionality of frecency and bringing up likely web pages.  I, and many users I know, have come to rely on this one stop search and find box.  TaskFox should improve upon it, but should not interrupt it.  Additionally, it would be nice to give the user an opportunity to discover more commands, possibly through the drop down that you have slotted, or by mixing them into the awesome bar results (though a system would have to be devised which would do this with discretion, not listing more than two or three).  Above all, in order to have a successful adoption and browser, remember that Taskfox is an extension of the awesomebar, not a new application.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nils</title>
		<link>http://blog.mozilla.com/faaborg/2009/03/25/integrating-ubiquity-into-firefox-ui-mockups/comment-page-1/#comment-126580</link>
		<dc:creator>Nils</dc:creator>
		<pubDate>Fri, 27 Mar 2009 09:19:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=82#comment-126580</guid>
		<description>Neither &#039;ebay&#039; nor &#039;Amazon&#039; nor &#039;Skype&#039; are actions/commands, they are company names. So the &#039;skype action&#039; could be a) phone the contact entered b) chat with th contact entered c) search for a user in the skype directory d) add a user to the contact list…

How does the application decide what to do? How will the user know what happens except he tries out all of them?

Sorry, but very inconsistet as for now.</description>
		<content:encoded><![CDATA[<p>Neither &#8216;ebay&#8217; nor &#8216;Amazon&#8217; nor &#8216;Skype&#8217; are actions/commands, they are company names. So the &#8216;skype action&#8217; could be a) phone the contact entered b) chat with th contact entered c) search for a user in the skype directory d) add a user to the contact list…</p>
<p>How does the application decide what to do? How will the user know what happens except he tries out all of them?</p>
<p>Sorry, but very inconsistet as for now.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Raiz</title>
		<link>http://blog.mozilla.com/faaborg/2009/03/25/integrating-ubiquity-into-firefox-ui-mockups/comment-page-1/#comment-126460</link>
		<dc:creator>Greg Raiz</dc:creator>
		<pubDate>Fri, 27 Mar 2009 01:01:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=82#comment-126460</guid>
		<description>I like idea #1 but I think the layout is perhaps inverted.  The action/verb is on the left but then you type the URL to the right. 

I would expect the verb drop-down would be on the left side, so you choose your action first then type then Go. 

Also off of idea #1 I would add a drag handle for things like the map so you could drag-drop it into an email.</description>
		<content:encoded><![CDATA[<p>I like idea #1 but I think the layout is perhaps inverted.  The action/verb is on the left but then you type the URL to the right. </p>
<p>I would expect the verb drop-down would be on the left side, so you choose your action first then type then Go. </p>
<p>Also off of idea #1 I would add a drag handle for things like the map so you could drag-drop it into an email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fullmetaljacket</title>
		<link>http://blog.mozilla.com/faaborg/2009/03/25/integrating-ubiquity-into-firefox-ui-mockups/comment-page-1/#comment-126197</link>
		<dc:creator>fullmetaljacket</dc:creator>
		<pubDate>Thu, 26 Mar 2009 09:46:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=82#comment-126197</guid>
		<description>just fyi, i am getting a &quot;Reported Attack Site&quot; message when i click the link to blair&#039;s blog post.</description>
		<content:encoded><![CDATA[<p>just fyi, i am getting a &#8220;Reported Attack Site&#8221; message when i click the link to blair&#8217;s blog post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pd</title>
		<link>http://blog.mozilla.com/faaborg/2009/03/25/integrating-ubiquity-into-firefox-ui-mockups/comment-page-1/#comment-126158</link>
		<dc:creator>pd</dc:creator>
		<pubDate>Thu, 26 Mar 2009 08:32:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=82#comment-126158</guid>
		<description>I like the first idea best because it appears to be heading towards the idea of merging the search bar with one all-powerful customisable awesome command bar.

After all, that is what the &#039;location&#039; bar should be - one all-powerful &#039;multimedia&#039; GUI command line to access the www.

One problem will be ensuring that there is clarity around what should take priority. Example: someone makes a command to &quot;google myself&quot;. How does the UI react? A) Send a search query for &quot;myself&quot; to Google? B) Grab the command from a ubiquity setting and search Google for &quot;Joe Citizen&quot;?</description>
		<content:encoded><![CDATA[<p>I like the first idea best because it appears to be heading towards the idea of merging the search bar with one all-powerful customisable awesome command bar.</p>
<p>After all, that is what the &#8216;location&#8217; bar should be &#8211; one all-powerful &#8216;multimedia&#8217; GUI command line to access the www.</p>
<p>One problem will be ensuring that there is clarity around what should take priority. Example: someone makes a command to &#8220;google myself&#8221;. How does the UI react? A) Send a search query for &#8220;myself&#8221; to Google? B) Grab the command from a ubiquity setting and search Google for &#8220;Joe Citizen&#8221;?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Albert</title>
		<link>http://blog.mozilla.com/faaborg/2009/03/25/integrating-ubiquity-into-firefox-ui-mockups/comment-page-1/#comment-126156</link>
		<dc:creator>Albert</dc:creator>
		<pubDate>Thu, 26 Mar 2009 08:26:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.mozilla.com/faaborg/?p=82#comment-126156</guid>
		<description>Nice to see that your first suggestion is a mix of the location bar, search bar and Ubiquity keywords. I think that its a very logical starting point: why need a specialized bar for searching when it can be done as part of the awesomebar?

However, I&#039;m not really fond of the discoverability by dropdown. Perhaps something like this is smarter: you type in something and the action buttons appear in a horizontal list at the bottom of the action preview. Clicking on one will then switch the preview to the desired action. Double clicking or pressing enter after that will actually perform the action. I guess that the action &#039;button&#039; is not really a button anymore (who doubleclicks a button?) but the idea is clear, right?</description>
		<content:encoded><![CDATA[<p>Nice to see that your first suggestion is a mix of the location bar, search bar and Ubiquity keywords. I think that its a very logical starting point: why need a specialized bar for searching when it can be done as part of the awesomebar?</p>
<p>However, I&#8217;m not really fond of the discoverability by dropdown. Perhaps something like this is smarter: you type in something and the action buttons appear in a horizontal list at the bottom of the action preview. Clicking on one will then switch the preview to the desired action. Double clicking or pressing enter after that will actually perform the action. I guess that the action &#8216;button&#8217; is not really a button anymore (who doubleclicks a button?) but the idea is clear, right?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

