<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Robert Accettura&#039;s Fun With Wordage &#187; fennec</title>
	<atom:link href="http://robert.accettura.com/blog/tag/fennec/feed/" rel="self" type="application/rss+xml" />
	<link>http://robert.accettura.com</link>
	<description>Robert Accettura&#039;s Personal Blog on Web Development and Tech</description>
	<lastBuildDate>Thu, 09 Feb 2012 01:43:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<atom:link rel='hub' href='http://robert.accettura.com/?pushpress=hub'/>
<cloud domain='robert.accettura.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
		<item>
		<title>No Opera For iPhone</title>
		<link>http://robert.accettura.com/blog/2008/10/31/no-opera-for-iphone/</link>
		<comments>http://robert.accettura.com/blog/2008/10/31/no-opera-for-iphone/#comments</comments>
		<pubDate>Sat, 01 Nov 2008 02:45:52 +0000</pubDate>
		<dc:creator>Robert</dc:creator>
				<category><![CDATA[Mozilla]]></category>
		<category><![CDATA[fennec]]></category>
		<category><![CDATA[firefox mobile]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[licensing]]></category>
		<category><![CDATA[opera]]></category>

		<guid isPermaLink="false">http://robert.accettura.com/?p=2096</guid>
		<description><![CDATA[I&#8217;m not to thrilled to read this: Mr. von Tetzchner said that Opera’s engineers have developed a version of Opera Mini that can run on an Apple iPhone, but Apple won’t let the company release it because it competes with &#8230; <a href="http://robert.accettura.com/blog/2008/10/31/no-opera-for-iphone/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m not to thrilled to read <a href="http://bits.blogs.nytimes.com/2008/10/27/opera-sings-an-ode-to-browsers-everywhere/">this</a>:</p>
<blockquote cite="http://bits.blogs.nytimes.com/2008/10/27/opera-sings-an-ode-to-browsers-everywhere/"><p>
Mr. von Tetzchner said that Opera’s engineers have developed a version of Opera Mini that can run on an Apple iPhone, but Apple won’t let the company release it because it competes with Apple’s own Safari browser.
</p></blockquote>
<p>This isn&#8217;t news, it&#8217;s been <a href="http://blog.mozilla.com/rob-sayre/2008/03/06/apple-bans-firefox-spidermonkey-lisp-lua-ruby-python-rhino-java-opera-gcc/">known for a while</a>.  I&#8217;m honestly wondering why Opera invested the development time with this in mind.</p>
<p>Apple&#8217;s going to learn the hard way that if it doesn&#8217;t drop this clause it&#8217;s going to be subject to Android&#8217;s wrath.  Android is going to take some time to gather steam (I&#8217;d guess at least 18 months before it can catch up to the iPhone due to it still being pretty clunky and limited in availability) but when it does it catch up, it could be problematic.</p>
<p>It would be great to see a iPhone version of <a href="http://www.mozilla.org/projects/fennec/1.0a1/releasenotes/">Fennec</a>, but until Apple wises up, it&#8217;s not going to happen.</p>
<p>I predict just like Apple initially had a &#8220;no third party applications&#8221; policy, this too will change once it becomes obvious that this will end up hurting them in the long run.  The question remains: how long will that take?
<div id="rja_commentCountImage"><a href="http://robert.accettura.com/?p=2096#comments"><img src="http://robert.accettura.com/wp-content/commentCount/2008/11/194cf6c.gif" alt="Comment Count" style="border:0;" /></a></div>
]]></content:encoded>
			<wfw:commentRss>http://robert.accettura.com/blog/2008/10/31/no-opera-for-iphone/feed/</wfw:commentRss>
		<slash:comments>7</slash:comments>
		</item>
		<item>
		<title>Mobile Browsing UI</title>
		<link>http://robert.accettura.com/blog/2008/09/27/mobile-browsing-ui/</link>
		<comments>http://robert.accettura.com/blog/2008/09/27/mobile-browsing-ui/#comments</comments>
		<pubDate>Sun, 28 Sep 2008 01:54:37 +0000</pubDate>
		<dc:creator>Robert</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Mozilla]]></category>
		<category><![CDATA[fennec]]></category>
		<category><![CDATA[safari]]></category>
		<category><![CDATA[user-interface]]></category>
		<category><![CDATA[web browsers]]></category>

		<guid isPermaLink="false">http://robert.accettura.com/?p=2019</guid>
		<description><![CDATA[It&#8217;s interesting to watch mobile web browsing UI develop. This is really the first time since web browsers existed that they have received a large overhaul. Sure things like tabs are &#8220;major&#8221;, but when you really look at it, Safari, &#8230; <a href="http://robert.accettura.com/blog/2008/09/27/mobile-browsing-ui/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>It&#8217;s interesting to watch mobile web browsing UI develop.  This is really the first time since web browsers existed that they have received a large overhaul.  Sure things like tabs are &#8220;major&#8221;, but when you really look at it, Safari, Chrome, IE, Firefox are all strikingly similar to the original Mosaic (this is 1.0 running on Windows XP):</p>
<p><img src="http://robert.accettura.com/wp-content/uploads/2008/09/20080927_ncsa_mosaic_ui.png" alt="NCSA Mosaic UI" class="centered size-full wp-image-2020" /></p>
<p>I&#8217;m not sure who&#8217;s idea it was to put the title in the UI like that, especially in a time when displays were small.  That was a gigantic waste of space.  The address bar in this version is read only, you need to select open and enter your URL there.  Other than that, it&#8217;s pretty much the same browser UI since 1993.  That&#8217;s right, 15 years of really the same user interface.  The window to the web has always looked that way.  There&#8217;s now bookmarking, a fancier address bar, favicons, and a search box.  Firefox goes nuts by letting users install add-ons.  Overall: Not very different. </p>
<p>There&#8217;s a few reasons why it hasn&#8217;t changed too much.  First of all, it&#8217;s a pretty good design.  Minus some quirks which were worked out pretty fast, it&#8217;s effective.  If it wasn&#8217;t the web wouldn&#8217;t have caught on.  Secondly, people know how to use it already.  Why make people re-learn?</p>
<p>The mobile space is different yet surprisingly the same.  Like days of old there&#8217;s a need to conserve screen space.  Unlike days of old there&#8217;s no reason to believe it will get bigger since small phones are always desirable.  Until screens are foldable, the iPhone is about as big as you&#8217;ll see.  Even when phones get thinner and lighter, the screen size won&#8217;t likely get any larger since it will be awkward to hold and put in your pocket.</p>
<p>With a touch screen you can only make items in the UI as small as a fingerprint.  Any smaller and they are unusable to people.  A stylus while clunkier and more awkward allows for a much more compact UI.  This leaves very little space to get a lot accomplished.  Too add to the complexity of the problem websites are designed for big displays meaning there&#8217;s a lot to cram into a small space.</p>
<p>Apple&#8217;s allegedly making a <a href="http://blog.wired.com/gadgets/2008/09/iphone-22-safar.html">pretty interesting change</a> to iPhone 2.2.  Safari will break out the search box into a more desktop-like separate box.  This results in a smaller address bar and the reload icon being moved inside the url bar.  I think the reason for this is to better parody the desktop, and remind users they can search from the browser chrome.</p>
<p><img src="http://robert.accettura.com/wp-content/uploads/2008/09/20080927_iphone-safari.jpg" alt="iPhone 2.2 Safari With Search Box" class="centered size-full wp-image-2021" /></p>
<p>To be perfectly honest, I&#8217;m not sure the address bar is even needed in a mobile browser on a touchscreen device.  Unlike a desktop you can&#8217;t type directly into it because of the small size.  Your essentially going to another UI to enter the text anyway.  Why not just make it a button?  You could argue you need the address bar as a way to know where you are.  Of course you can likely merge it with the Title to accomplish that.  All that&#8217;s needed in the main UI is the title and hostname.  That can be all in the title of the window.  I think I&#8217;d prefer a back button more than the address bar on a mobile device.  Of course if I could tap or tilt the device to go backwards or forwards that would be cool too.  One less thing for the UI.</p>
<p>The most similar to this is <a href="https://wiki.mozilla.org/Mobile/UI/Designs/TouchScreen/workingUI">Fennec</a>. </p>
<p>On a side note, thanks to Apple&#8217;s insane SDK licensing and app store policy it is unlikely to ever live on an iPhone.  Maybe one day Apple will realize that just like 3rd party applications (something they were originally against), an even more open device would be even more enticing.  But I digress.</p>
<p><img src="http://robert.accettura.com/wp-content/uploads/2008/09/20080927_nintendo_ds.jpg" alt="Nintendo DS" class="alignright size-full wp-image-2024" />Another concept I&#8217;d really love to see and experiment with is a dual screen format.  Similar to that of the Nintendo DS.  This would be perfect for a flip phone style smart phone. As phones can be made thinner folding them over is an option to keep the physical device small enough for portability but the display size can then be doubled.  By the time the iPhone can be made half the thickness (remember the iPod G1 was much thicker than it is now) this is feasible.</p>
<p>There are several fun things about this design.  First of all you essentially <a href="http://www.artlebedev.com/everything/optimus/">Optimus Maximus keyboard</a> on your phone.  Secondly you can now separate the content from the chrome in applications.  Perfect for things like web browsers.  This is also handy for watching movies as controls don&#8217;t overlay video but are still available.  It also would be great for multi-tasking.</p>
<p>That&#8217;s where I predict things will ultimately go.  We&#8217;re once again in the era of Bar form phones.  Anyone remember the Nokia 1100/5110/3210/3310 fad a few years ago?  Then flip phones came back in style.  The flip phone style also has the advantage of protecting the internal display from scratches and involuntary button pressing.</p>
<p>It will be fun to see how the interface evolves.  I&#8217;m relatively certain despite all the different UI prototypes surfacing right now regarding web browsers, as they mature they will adopt features from each other and become surprisingly similar to each other.</p>
<p><small>iPhone Safari image via <a href="http://blog.wired.com/gadgets/2008/09/iphone-22-safar.html">Wired</a>.  Nintendo DS image via <a href="http://en.wikipedia.org/wiki/Image:Nintendo_DS_Trans.png">Wikipedia Commons</a>]</small>
<div id="rja_commentCountImage"><a href="http://robert.accettura.com/?p=2019#comments"><img src="http://robert.accettura.com/wp-content/commentCount/2008/09/ea6b2ef.gif" alt="Comment Count" style="border:0;" /></a></div>
]]></content:encoded>
			<wfw:commentRss>http://robert.accettura.com/blog/2008/09/27/mobile-browsing-ui/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

