<?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; n1</title>
	<atom:link href="http://blog.iangclifton.com/tag/n1/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>From Android To iOS, Usability Examined</title>
		<link>http://blog.iangclifton.com/2010/08/11/from-android-to-ios-usability-examined/</link>
		<comments>http://blog.iangclifton.com/2010/08/11/from-android-to-ios-usability-examined/#comments</comments>
		<pubDate>Thu, 12 Aug 2010 01:25:08 +0000</pubDate>
		<dc:creator>Ian G. Clifton</dc:creator>
				<category><![CDATA[Mobile Devices]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[apple]]></category>
		<category><![CDATA[ios]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[n1]]></category>
		<category><![CDATA[nexus one]]></category>
		<category><![CDATA[usability]]></category>

		<guid isPermaLink="false">http://blog.iangclifton.com/?p=274</guid>
		<description><![CDATA[When I first starting doing development for smartphones, my job was purely on the web side of things, and I didn&#8217;t even have a smartphone. I had a lowly LG Shine (which I was actually very happy with and held &#8230; <a href="http://blog.iangclifton.com/2010/08/11/from-android-to-ios-usability-examined/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>When I first starting doing development for smartphones, my job was purely on the web side of things, and I didn&#8217;t even have a smartphone.  I had a lowly LG Shine (which I was actually very happy with and held onto for another 8 months after starting my current job), so I regularly carried one of the dev iPhones from work on me.  I played around with it quite a bit on the bus ride in and out of Seattle half to learn what the user experience was like and half to figure out why so many people were obsessed with the iPhone.  After several months, I finally caved&#8230; and bought a Nexus One.  It was both a better choice philosophically and technologically <em>for me</em>.</p>
<p>Though I use my Nexus One for all my mobile needs, I still occasionally have to test things with the iPhone, and I&#8217;ve found that switching back is quite frustrating.  Everyone touts the usability and user interface of iOS while commenting on how far Android has to go, but I&#8217;m definitely willing to take a stand and say iOS has plenty of issues of its own, big and small.<span id="more-274"></span></p>
<p><strong>Keyboard</strong><br />
I was extremely used to the iPhone keyboard, so I initially found myself a bit slower, making occasional mistakes on the Nexus One.  Now, when I try to use the iPhone keyboard, I am constantly hitting the wrong keys.  I think that both keyboards are good, but you certain get used to a specific one.  That said, there are some simple features that make the Android keyboard(s) better than iPhone&#8217;s.  For instance, I keep the sound off on the keyboards I use, so I love the haptic feedback (slight vibration) I get with an Android device and typing on an iPhone feels, well, <em>flat</em> in comparison.  I don&#8217;t have a sense of pressing any keys.  The iPhone keyboard doesn&#8217;t even change the appearance of the letters to show if I am typing a capital letter or not.  With Android, I&#8217;ve tried a few different keyboards, the default, <a href="http://www.swypeinc.com/">Swype</a>, and my personal favorite, <a href="http://www.swiftkey.net/">SwiftKey</a>, and I am <em>much</em> faster typing on an Android device.</p>
<p><strong>Email</strong><br />
So here you are, typing an email on an iPhone when you suddenly realize you forgot to include this great picture that you took earlier.  There&#8217;s no way to attach that image to the email now, whoops!  In Android, you would simply press menu, attach, pick the program you want to use to select the file, and then pick the file.  Another thing that really surprised me is the inability to configure sounds for email (or many other things for that matter&#8230; and why are app-specific settings not in the app they are for?).  On my Nexus One, I have a different sound for my work account than for my personal accounts, so I know which account the email is for just from the sound.  When the default new email sound plays on an iPhone at work, the half dozen iPhone owners nearby all check their iPhones.</p>
<p><strong>Now opening your app&#8230; wait for it&#8230;. wait for it&#8230;.</strong><br />
When I open an app on my N1, it is instantly open; few apps take more than a second to animate in.  When I open an app on an iPhone, I get a fancy splash screen and then I get to wait.  Well, that&#8217;s when the app developer actually bothered to make a splash screen.  A lot of the built-in apps don&#8217;t have splash screens (Photos, Calendar, Clock, etc.), so you get a partial load and then a slight delay, and then the useful stuff appears.  To be fair, as iPhone hardware has slowly improved, this is a bit less of a problem for each new iteration.  Still, waiting is frustrating, and it&#8217;s even worse on pre-iOS 4 apps that don&#8217;t save state.</p>
<p><strong>App Store</strong><br />
I really can&#8217;t believe this app is so bad.  It&#8217;s extremely slow, categories aren&#8217;t even in alphabetical order, and it appears to do a screen dump if the phone sleeps for a few minutes.  That last one is especially annoying on the dev iPhone that doesn&#8217;t have cell access because WiFi turns off after a bit, which means I get the &#8220;Cannot Connect to App Store&#8221; error message when the phone turns back on instead of simply seeing the page I was <em>just</em> looking at.</p>
<p><strong>Quick access to info</strong><br />
Okay, so maybe some readers came across the previous two issues and thought, &#8220;Pssh, this doesn&#8217;t affect my speedy iPhone 4.&#8221;  Perhaps not, but let me ask this: &#8220;How long does it take you to check the current date or weather?&#8221;  Despite the much faster hardware, the OS really slows down the user experience for me.  Obviously you can&#8217;t use widgets in iOS, but you don&#8217;t have to use widgets for these tasks in Android.  You can just use the notification bar.  The WeatherBug app can keep the current temperature in the notification bar, which you can also slide down for a forecast and to see the current date (standard part of Android).  Want to see what that email is about that you just got?  Simply slide down the notification bar to view a preview.  These are simple tasks that I do a lot, so I don&#8217;t like the extra effort that they take on an iPhone.</p>
<p><strong>New version, now go find a computer</strong><br />
The iPhone&#8217;s inability to be an independent computing devices was one of the biggest technological turn offs for me when I was considering it.  Really, why can&#8217;t I get OS updates over the air (even if it&#8217;s limited to just WiFi because of the tired &#8220;AT&#038;T&#8217;s network is overloaded&#8221; excuse)?  The iTunes umbilical cord is even more annoying for those of us who use Linux as our primary OS.</p>
<p><strong>There&#8217;s an app for that&#8230;. somewhere</strong><br />
Say a friend sends you a link to a Twitter account that he finds funny.  You tap that link and open the browser, it redirects to the mobile version and then you see the content (assuming Twitter is somehow not down).  Of course an app would be a better experience, so you have to very carefully copy the username from the URL and then press the home button, scroll to the right a bunch of screens, open your Twitter app, go to the search feature, paste the username, and search.  On Android, an app can register to handle URLs, so tapping that link immediately gives you the open to open it in the browser or the Twitter app(s).  Similarly, sharing a URL is as simple as long-pressing it, picking share, and then picking the app.</p>
<p><strong>The other stuff</strong><br />
Why don&#8217;t the volume buttons control the volume of sound effects while I am playing a game?  Why do I have to turn on the phone to check if I missed any emails/phone calls/text messages?  Why are the home screens just a dump of the application list?  Why do I have to scroll to the top of a web page to enter a new address?  I guess the trick is to open the tab selector and close the current tab then pick New Page, but that still seems a bit excessive.  There is a lot of value in having some basic buttons for your phone, especially for things that are useful in 99% of apps (back? menu?), and, <a href="Three of the four shouldn't be there.">unlike some iPhone advocates</a>, I find the lack of buttons annoying.  Fortunately, Apple is fairly good about enforcing <em>their</em> way of doing things, so apps usually behave in a pretty consistent way, implementing menus and back button in the app in a similar manner at the expense of screen real estate.</p>
<p>In the end, now that I am fully accustomed to my Nexus One, I have to say that <strong>I find it much more usable than iPhones</strong>.  Not only is it more feature-rich, but it is truly a much better user experience for me.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.iangclifton.com/2010/08/11/from-android-to-ios-usability-examined/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>
		<item>
		<title>Not Eligible For T-Mobile Nexus One</title>
		<link>http://blog.iangclifton.com/2010/01/05/not-eligible-for-t-mobile-nexus-one/</link>
		<comments>http://blog.iangclifton.com/2010/01/05/not-eligible-for-t-mobile-nexus-one/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 07:07:29 +0000</pubDate>
		<dc:creator>Ian G. Clifton</dc:creator>
				<category><![CDATA[Mobile Devices]]></category>
		<category><![CDATA[google]]></category>
		<category><![CDATA[n1]]></category>
		<category><![CDATA[nexus one]]></category>
		<category><![CDATA[tmobile]]></category>

		<guid isPermaLink="false">http://blog.iangclifton.com/?p=87</guid>
		<description><![CDATA[If you haven&#8217;t heard, the Nexus One (N1) has been released. It&#8217;s the newest Android-based phone, built by HTC and being &#8220;pushed&#8221; by Google. Unfortunately, ordering one has caused trouble for many people, myself included. Rather than paying $400 for &#8230; <a href="http://blog.iangclifton.com/2010/01/05/not-eligible-for-t-mobile-nexus-one/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://blog.iangclifton.com/wp-content/uploads/2010/01/nexus-one-not-eligible.png"><img src="http://blog.iangclifton.com/wp-content/uploads/2010/01/nexus-one-not-eligible-400x208.png" alt="Nexus One, Not Eligible" title="Nexus One, Not Eligible" width="400" height="208" class="aligncenter size-medium wp-image-88" /></a></p>
<p>If you haven&#8217;t heard, the <a href="http://www.google.com/phone">Nexus One</a> (N1) has been released.  It&#8217;s the newest Android-based phone, built by HTC and being &#8220;pushed&#8221; by Google.  Unfortunately, ordering one has caused trouble for many people, myself included.<span id="more-87"></span></p>
<p>Rather than paying <a href="/2009/10/03/mobile-phones-and-customer-loyalty/">$400 for an iPhone via AT&#038;T</a>, I thought getting the $180 N1 would be a great deal, especially since I could switch to T-Mobile and pay just $80 a month for the plan (less expensive than either Verizon or AT&#038;T).  Unfortunately, I filled out the form and got the error: &#8220;You are not eligible for T-Mobile service at this time.&#8221;</p>
<p>Sadly, that&#8217;s all the info Google provides, other than comforting me with the option of buying it straight up for $530.  I have no idea why I am ineligible.  My roommate has a G1 on T-Mobile, so service is available.  I have never had a contract with T-Mobile, so it&#8217;s not a matter of being an existing or past customer ineligible for upgrade.  I&#8217;ve <a href="http://www.t-mobile.com/switch/">checked to make sure I can transfer my phone number</a>, and it&#8217;s eligible for transfer.  Why am I not eligible?</p>
<p><strong>Update!  Success!</strong><br />
I did it again and changed two things, and it worked.  I&#8217;m not sure which of these two mattered, but here they are in the hope that they&#8217;ll help someone else:</p>
<p>1) <a href="http://www.google.com/support/forum/p/Google+Mobile/thread?tid=074d6eaf320f1945&#038;hl=en">Per eperor&#8217;s suggestion</a>, I asked for a new phone number.</p>
<p>2) I changed my service area to downtown Seattle (where I work) rather than my home address.</p>
<p>This worked for me; good luck to everyone else!</p>
<p><a href="http://blog.iangclifton.com/wp-content/uploads/2010/01/purchased-nexus-one.png"><img src="http://blog.iangclifton.com/wp-content/uploads/2010/01/purchased-nexus-one-400x194.png" alt="Purchased Nexus One" title="Purchased Nexus One" width="400" height="194" class="aligncenter size-medium wp-image-94" /></a></p>
]]></content:encoded>
			<wfw:commentRss>http://blog.iangclifton.com/2010/01/05/not-eligible-for-t-mobile-nexus-one/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

