<?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>A Dash of Web and Mobile Development &#187; g1</title>
	<atom:link href="http://blog.iangclifton.com/tag/g1/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.iangclifton.com</link>
	<description>Discussing trends and technologies in web and mobile development</description>
	<lastBuildDate>Fri, 03 Feb 2012 05:15:35 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Hardware Buttons And Screen Size</title>
		<link>http://blog.iangclifton.com/2011/02/07/hardware-buttons-and-screen-size/</link>
		<comments>http://blog.iangclifton.com/2011/02/07/hardware-buttons-and-screen-size/#comments</comments>
		<pubDate>Tue, 08 Feb 2011 03:36:39 +0000</pubDate>
		<dc:creator>Ian G. Clifton</dc:creator>
				<category><![CDATA[Mobile Devices]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[g1]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[nexus one]]></category>
		<category><![CDATA[nexus s]]></category>

		<guid isPermaLink="false">http://blog.iangclifton.com/?p=387</guid>
		<description><![CDATA[An interesting trend with Android phones (at least, in the US) is that they&#8217;re mostly being built with larger and larger screens. The G1 (HTC Dream) has a 3.2&#8243; screen, the Nexus One has a 3.7&#8243; screen, and the Nexus &#8230; <a href="http://blog.iangclifton.com/2011/02/07/hardware-buttons-and-screen-size/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>An interesting trend with Android phones (at least, in the US) is that they&#8217;re mostly being built with larger and larger screens.  The G1 (HTC Dream) has a 3.2&#8243; screen, the Nexus One has a 3.7&#8243; screen, and the Nexus S has a 4&#8243; screen.  The Android phones at CES were mostly in the 4-4.5&#8243; range.  I remember first hearing that the Evo 4G had a 4.3&#8243; screen, and I thought that surely such a screen was too big.  Then I used one in person and realized a larger touchscreen is a good thing and the slim bevels that Android phones typically feature now help keep the overall dimensions from significantly expanding.<span id="more-387"></span></p>
<p>There are a lot of advantages to a larger touchscreen, including making the UI easier to interact with because the hit areas can be larger.  The biggest drawback is power use, though displays are becoming significantly more efficient (take a look at the LG Nova, for instance).  The other would-be drawback is loss of portability, but consider this: The Evo 4G is only about seven millimeters wider and taller than the iPhone 4 despite having a screen that is 4.3&#8243; vs. 3.5&#8243; diagonally.  So why wouldn&#8217;t Apple increase the screen size of the iPhone?</p>
<p>There are several reasons, most of which are obvious.  The appearance has been roughly the same since the first version, so it&#8217;s easily recognizable.  The smaller screen gives the iPhone longer battery life (particularly with how efficient the iPhone 4 screen is).  The iPhone also has a higher percentage of female users who are more likely to have small hands (of course, they could offer more than one screen size, but that&#8217;s unlikely).</p>
<p><a href="http://blog.iangclifton.com/wp-content/uploads/2011/02/iphone-compose-mail.png"><img src="http://blog.iangclifton.com/wp-content/uploads/2011/02/iphone-compose-mail-200x300.png" alt="" title="iPhone New Email" width="200" height="300" class="alignleft size-medium wp-image-388" /></a></p>
<p>The reason that I don&#8217;t think is as obvious is the lack of a hardware back button, which is probably counterintuitive.  Without a hardware back button, the iPhone could remove a lot of that wasted bezel (since you don&#8217;t need space for that physical button) and fit a much larger screen, but that&#8217;s a problem.  The iPhone relies on software back buttons, which virtually every app implements, and the standard is to put them in the top left as a cancel or back button.  If you&#8217;re using your phone with your right hand, that means stretching to the farthest corner of the device.  When you&#8217;re looking at a screen that&#8217;s more than four inches diagonally, many people simply can&#8217;t stretch that far.</p>
<p>Contrast that with an Android phone where the back button is at the bottom (in portrait mode), so you can reach it easily.  Phones are typically only a couple of inches wide, so the buttons are easily accessible regardless of how you&#8217;re holding the device.  The screen can be 3&#8243; or 5&#8243; and not be affected.</p>
<p>Large tablets where your thumbs can&#8217;t reach across the device in portrait mode are a different matter and are much better candidates for on-screen buttons, so the buttons can be positioned close to where you actually hold the device (along the bottom of a given orientation).  I&#8217;m excited to see how UI shifts as more and more tablets emerge, especially with the potential for a variety of operating systems.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.iangclifton.com/2011/02/07/hardware-buttons-and-screen-size/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nexus One Debugging In Ubuntu Linux</title>
		<link>http://blog.iangclifton.com/2010/04/08/nexus-one-debugging-in-ubuntu-linux/</link>
		<comments>http://blog.iangclifton.com/2010/04/08/nexus-one-debugging-in-ubuntu-linux/#comments</comments>
		<pubDate>Fri, 09 Apr 2010 04:01:14 +0000</pubDate>
		<dc:creator>Ian G. Clifton</dc:creator>
				<category><![CDATA[Mobile Development]]></category>
		<category><![CDATA[adb]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[g1]]></category>
		<category><![CDATA[htc]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[n1]]></category>
		<category><![CDATA[nexus one]]></category>
		<category><![CDATA[ubuntu]]></category>

		<guid isPermaLink="false">http://blog.iangclifton.com/?p=179</guid>
		<description><![CDATA[This is mostly just a note to myself, but I figured some other people might find it useful. When I connected my Nexus One, it was showing up as &#8220;???????????? no permissions&#8221; when I ran adb devices. I added the &#8230; <a href="http://blog.iangclifton.com/2010/04/08/nexus-one-debugging-in-ubuntu-linux/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>This is mostly just a note to myself, but I figured some other people might find it useful.  When I connected my Nexus One, it was showing up as &#8220;????????????	no permissions&#8221; when I ran <code>adb devices</code>.  I added the typical udev rule and had no luck.  Running <code>lsusb</code> revealed the the vendor ID is different from the HTC G1.  So, to enable debugging this device and the G1 in Ubuntu (and other flavors of Linux), create/edit <code>/etc/udev/rules.d/51-android.rules</code> and put the following in it:</p>
<p><code>SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"<br />
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"</code></p>
<p>You may need to run <code>sudo reload udev</code> and/or disconnect and reconnect the N1.  Check <code>adb devices</code> again and hopefully you&#8217;ll see &#8220;HT9CSP123456	device&#8221; or similar.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.iangclifton.com/2010/04/08/nexus-one-debugging-in-ubuntu-linux/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

