Sharing URLs
A really handy feature that I didn’t know about until recently is the ability to share a URL you are viewing in the browser. Long-pressing on a URL in the location bar brings up a menu with the option to “Share page” or “Copy page url” (it can also include “Save image” and “View image” depending on the context). Choosing “Share page” reveals a menu with several options. At the top are the built-in choices such as sharing “@Delicious,” but below those you can see options for specific apps. Selecting “Twidroid” allows you to share the link via Twitter from right there. You don’t have to open the full Twidroid application, and you don’t have to worry about the URL length (as it’s automatically shortened with your URL shortener of choice). Just type a few words and send away. You can even hit “Attach” to add or take a picture or video (both of which are automatically uploaded and linked for you). I don’t care if you call this “multitasking” or “app interlinking.” I call it awesome.

Shortcuts
Most people already know that Android has folders, and it even has live folders (folders which have their contents populated by an app, such as a list of Pandora radio stations), but Android also has the ability to create shortcuts. I don’t just mean shortcuts to open apps; I mean shortcuts to open very specific parts of apps.

One of the applications that I use fairly frequently is One Bus Away, which allows me to see which buses are going where and when they should arrive. The default view that opens is a map view, which I personally don’t use. I know the stops I use and the routes I ride, so I nearly always want to go to a specific stop. I’m frequently in a hurry, checking if I’ll be seconds away from catching the bus, and the slight delay going from loading the map view to loading the stop I want feels a lot longer than it really is. Fortunately, Android has the answer: I can create a shortcut directly to the exact stop that I want to view. I simply long-press on the home screen, select “Shortcuts,” select the desired choice, (potentially further customize it, such as picking a specific bus stop in this case) and the icon is created. Touching that icon will jump right to the correct spot in the app.

Conclusion
These are the types of features that are so simple but add so much to the experience of using an Android-based device. Is Android perfect? Of course not. But can it do some amazing things? Absolutely!

SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", SYSFS{idVendor}=="18d1", MODE="0666"

You may need to run sudo reload udev and/or disconnect and reconnect the N1. Check adb devices again and hopefully you’ll see “HT9CSP123456 device” or similar.

First off, we have to clarify the concept of multitasking. On a desktop, notebook, netbook, etc., you will frequently have multiple programs open at a time and often more than one is visible on the screen. In most cases, these programs are actively running (usually with priority given to the application in focus) and using some processing cycles. Sometimes the background applications do need to use resources, such as an instant messaging client or music player. Sometimes they don’t, such as when you are actively playing a game but left a browser window open in the background.

The misconception is that Android handles all these processes the same way, forcing them to fight it out in a cage match with the winner getting processor cycles. Fortunately, that is not the case.

Unnecessary Processing
Most of the time the limited screen real estate means you don’t need background processes running for applications that don’t currently show any UI. Essentially, the processing associated with an activity ends, but the activity remains in memory until that memory is either needed or the activity is back in focus (obviously this is a bit of a simplification). When an activity goes into the background like this, it typically does any saving necessary. That allows the memory to be recovered aggressively, if needed, without creating delay at the time of recovery.

Some iPhone apps actually have similar behavior, but they store their state to the phone’s storage rather than the memory. This allows you to reopen an app, starting from the same point you ended it. Clearly, both Apple and iPhone developers see this ability to quickly switch tasks as valuable, despite that it isn’t “built in” to iPhone OS.

Necessary Processing
The other key situation is something called a service, and this is where the differences between Android and iPhone OS are most noticeable. A service is a process that does not directly have UI or an activity associated with it. A process for handling the reception of instant messages is a good example. You don’t want to sit on a screen all day to wait for new messages. You want to be able to check your email, browse the web, or play a game. The service can run in the background and unobtrusively notify you of new messages.

Apple’s Situation
Apple sees the need for some apps to have background processes; the music player is a good example. Apple just hasn’t fully opened the door to letting the third-party developers run background processes. Instead, they allow for push notifications.

But push notifications are not the complete answer. They have an extremely limited 256-byte maximum payload. They are not secure. They require extra infrastructure. They overwrite each other. They are designed for text only. The application cannot manipulate the push notification data if it is not running. And, worst of all, push notifications are extremely intrusive! Implemented properly, push notifications could be the correct solution for some situations, but they currently present a bad user experience and have limited value to developers.

Additional Uses
Besides music players, instant messengers, and SSH connections, location-based services like Google Latitude are virtually useless without background processes. Another example of a background service is common in feed readers such as NewsRob. While you don’t have the app open in the foreground, it is still able to periodically fetch new feed items. That means you can later open that app without an internet connection and still read your favorite feeds. With iPhone, you have to actively open each app and tell it to cache the data for offline reading, wait, and then repeat for each app you might want to use (such as during a plane ride).

Even if you disagree
Finally, even if you believe nothing of what I have written and still believe that background processes waste a huge amount of processor cycles and drain your battery, then you should ask yourself how the Nexus One has a battery life comparable to the iPhone’s when it has a faster processor that is pushing more than twice as many pixels, it has more RAM, it runs third-party background applications… not to mention the battery is user-replaceable ($25 for an Android battery; roughly four times that for Apple to replace an iPhone battery). It must be from HTC stealing Apple’s innovation again *sigh*.

Here’s the disclaimer: I did my best to fairly show the differences between the screens of a Nexus One and an iPhone. Both phones were set to maximum brightness and were indirectly lit in an attempt to avoid glare. The Nexus One has a much greater tendency to reflect light than the iPhone. The camera (Canon 7D) was set to output to JPG because I didn’t want to subconsciously favor one display over the other when processing from RAW. The full-sized images are around 7MB each, so I created a resized version (1024×683 from 5184×3456) and, in some cases, a detailed version. The detailed version is a crop from the original image with no resizing. I just took two 512×683 crops and put them together. I didn’t label them because the Nexus One is always on the left and the iPhone is always on the right. Images embedded in this post are 400 pixels wide and link to the larger versions.

Home Screen

The iPhone’s home screen looks rather bland compared to the Nexus One. The icons are fairly similar, though you can see that the Nexus One icons are smaller and varying shapes (some iPhone 3rd party icons are different shapes, but transparency is not properly handled by the iPhone OS, so these only look transparent with a black background).

The Web – New York Times

For most people, the web browser will be the most used feature of a smartphone. These photos illustrate the difference that a higher resolution makes. Though the displays are close to the same physical size, small fonts are unreadable on the iPhone. I recommend viewing the full sized version of the detailed photo.

The Web – Image

Both phones are browsing a photo on Flickr, but you can see that the iPhone can’t display the full image at its native size (note that the Nexus One is actually zoomed in a bit on the image because the image is only 500px wide). The difference in the shadows is probably the most noticeable part of this comparison. The Nexus One appears to display oranges a bit brighter than it should. The iPhone loses detail in darker parts of the photo.

Maps – Satellite View

Though both displays a very usable, the Nexus One looks particularly crisp compared to the iPhone here.

Maps – Traffic View

I had a particularly challenging time getting these views to be zoomed identically across both displays, so don’t put too much emphasis on these. I did notice that the iPhone didn’t report construction on its maps application, but the overall data was basically the same. Again, the Nexus One appears much sharper.

PDF

Though you’re unlikely to read significant amounts on either phone, this PDF comparison shows the advantages of a higher pixel density. This also makes me question the recently-unveiled iPad as a serious reading device (its long side is only 1024 pixels, 224 more than the Nexus One, despite being much larger).

Apps – TV.com

As you can see, the TV.com app has a different interface on iPhone OS vs. Android. The Android version is able to show a lot more data at one time, though part of that is due to not needing a static menu on screen. During video playback, the actual video doesn’t take up the full width on the Nexus One. Here, you can see the greater range of colors on the Nexus One, particularly in the detailed photo. I also noticed that the iPhone’s black was a bit blue and not as dark as the Nexus One’s black. The Nexus One picked up a bit of glare but was still very usable.

Final Thoughts
One thing that really stood out during this test was how much more the Nexus One screen shows, and I don’t just mean in pixel count. Since Android has support for more than one button, applications do not have to waste screen space by displaying a menu. In most cases, that means displaying an extra row worth of information.

The Nexus One definitely has a more significant problem with glare, but it also has much darker blacks. It is a little over saturated around orange colors, though not significantly so. The iPhone screen does a good job of diffusing light, but the blacks never look fully black. The colors seem well balanced with less range, but the lower resolution really hurts the iPhone when it is next to the Nexus One.

If you haven’t heard, the Nexus One (N1) has been released. It’s the newest Android-based phone, built by HTC and being “pushed” by Google. Unfortunately, ordering one has caused trouble for many people, myself included.

Rather than paying $400 for an iPhone via AT&T, 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&T). Unfortunately, I filled out the form and got the error: “You are not eligible for T-Mobile service at this time.”

Sadly, that’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’s not a matter of being an existing or past customer ineligible for upgrade. I’ve checked to make sure I can transfer my phone number, and it’s eligible for transfer. Why am I not eligible?

Update! Success!
I did it again and changed two things, and it worked. I’m not sure which of these two mattered, but here they are in the hope that they’ll help someone else:

1) Per eperor’s suggestion, I asked for a new phone number.

2) I changed my service area to downtown Seattle (where I work) rather than my home address.

This worked for me; good luck to everyone else!