Here’s one, for example:
Issue 1664: Gmail should allow choosing the From: address on an account that has multiple addresses
Send As Feature in Gmail

For years, I’ve been using Thunderbird as my email client. I used it on Windows. Then I used it on Ubuntu. Then I used it on Mac OS X. Recently, inspired by my move to an Android phone, I decided to go as Google as possible. Google Voice. Google Docs. Google Maps. Google Reader. Gmail. There were some things that took adjusting to in Gmail (conversations instead of messages, anyone?), but I didn’t miss Thunderbird as much as I thought I would. Google gives you nigh-unlimited email storage (I don’t see meeting the 7 GB limit any time soon the way my emails are going), and the interface is simple and quick, and easy to use. More importantly, I can aggregate with Gmail a bunch of email accounts into one, just as I would with a traditional desktop email client (like Thunderbird, Mail, Eudora, or Outlook).

In the regular Gmail web interface, you can choose which of these accounts is the default email address (meaning if you compose a new message, that message will have the from: address be that email address unless you choose otherwise), and you can also choose to have all replies sent from the email the original message was sent to. That means if someone sends an email to my church account and I hit Reply, the reply will appear to come from my church account; and if someone sends an email to my home account and I hit Reply, the reply will appear to come from my home account.

Pretty nifty feature to have. Too bad it’s missing from Android’s Gmail app. In the Android Gmail app, if you compose a new message, it will always come from your Gmail email address, regardless of what your setting is on the web client. And if you reply to a message, it will also come from your Gmail address. That makes it pretty much useless to me in terms of writing emails, seeing as how I use my Gmail account to aggregrate other email accounts, and I basically never want emails to appear to come from my Gmail account.

Fortunately, there’s a workaround, but it’s not pretty. The workaround is not to use the Gmail app. Just use the Gmail web interface in your favorite Android browser (Browser, Opera, xScope, Dolphin, etc.). If you use the mobile version (which is the default) of the web client, you won’t actually get to see your from: address, but it’ll still operate the way it’s supposed to (I tested it on both a reply and a new email). You can switch to the desktop (or “classic”) mode of the web client if you actually want to see the from: address.

Now, Google, how difficult would it really be to fix this problem?

Yet two years ago when Asus was just starting to be successful with the Eee PC netbook (which came preinstalled with a version of Linux, which Microsoft had to stop right away by resurrecting XP for the first of many times to come), that’s what a lot of the press coverage assumed. Geez. I mean, a lack of advertising campaign or in-person models to try out in the store couldn’t have anything to do with Linux netbooks not selling. It must be that Linux is too hard to use. It must be that Linux isn’t ready for consumers. It must really be that consumers just prefer Windows when given the choice.

Well, there is some truth to that in that the Linux distro Asus chose to put on the Eee PC was essentially crippled (not at all like Ubuntu, PCLinuxOS, Fedora, Debian, OpenSuSE, or any of the other popular distros of the time). It wasn’t even vanilla Xandros. It was a custom Xandros that could be customized only through pasting cryptic commands in the terminal.

Nevertheless, if they’d marketed it correctly, Linux could have been a success. The problem with Linux on “the desktop” (or the laptop or netbook) is the myth of meritocracy. You don’t win by being the best. You win by marketing.

Think about it.

When the iPad was announced, critics focused on the features it didn’t have (no webcam, no Flash, no USB ports), but Apple with its clever marketing department convinced the hoards that the device was magic, so the hoards bought it. If a Linux tablet had been released without Flash, people would have just laughed and said “This is the reason Linux will never succeed—they need to realize the masses use Flash.” But Apple releases a tablet and all of a sudden people are actually saying Flash isn’t necessary. HTML5 is suddenly the wave of the future. Apps for websites are suddenly better than just going to the websites themselves.

I also see a lot of Linux poo-pooers claim Linux doesn’t have any apps, and that Windows users have certain killer apps they need, and that’s why Linux won’t succeed. Well, when Android first started, it had very few apps. In fact, for the end of 2008 and all through 2009, iPhone fanatics kept pointing out how many hundreds of thousands of apps the iTunes App Store had compared to the few thousand Android had. Well, Android now has almost 100,000 apps. If this pace continues, the iTunes App Store and Android Market will probably have the same number of apps by this time next year. The Linux desktop (as opposed to server or embedded) has been around since… the late 90s? Android has been around since 2008. The Linux desktop isn’t mainstream but Android is.

What should we learn from all this? Marketing matters. Being able to test a physical product out yourself matters. Dell selling badly marketed (or even anti-marketed) Ubuntu models on its website isn’t going to sell Ubuntu preinstalled in great numbers, nor are relatively obscure vendors like System76 or ZaReason without a proper store front or brand name recognition.

I would love it if all the bugs in Ubuntu (or some other popular Linux distro) could be fixed. I would love it if some more attention would be paid to ease of use or to making more applications available in the software repositories. I would love that. But that won’t fix Bug #1. If Linux wants to make a dent in the desktop/laptop/netbook world, it needs to give up the idea of being good enough and start embracing the idea of crafting, shipping, and marketing a product—yes, one people can try out in a brick-and-mortar store. In other words, what I said two years ago is still true.

Here are a few examples:

• Me: As some of my Ubuntu-using readers are dismayed about, I recently switched my primary operating system to Mac OS X on a Macbook Pro (still using Ubuntu on the netbook, still will keep updating Ubuntu tutorials). At the same time, I have an Android phone, and I will not be giving it up for an iPhone until Steve Jobs says (in all sincerity, not as a joke) “I love Google Voice and I think it’s the app everyone should install on the iPhone!” To make the most of my Android experience, I use GMail also, even to check my non-GMail accounts (via POP3). And, of course, I use Google as my main search engine.
• My wife: She’s an Apple user through and through. She uses a Mac at work, and she uses a Mac at home. She has an iPhone. She uses Mail, not Thunderbird or GMail. Safari (not Chrome) is her main web browser. At the same time, she has a Nook (Android-based) e-reader, and Google is still her main search engine.
• My pastor: Even this Apple hipster recently traded up his iPhone for an Android phone (albeit an iPhone clone), but he plans to get an iPad to keep up his “street cred.”
• My sister-in-law: She uses a Mac Mini with iTunes and has an iPod, but she also has an Android phone and a GMail and Google Voice account.
• My boss: She uses Google for just about everything. It’s her search engine. GMail is her email. She just got started with Google Voice the other day. She uses Picasa to organize her photos. But she’s an iPhone user.

In fact, I would say, at least among my social circle, the last example is the most typical. Yes, I know a lot of iPhone users. Before they had iPhones, they had iPods. Some of them still use iPods separately from their iPhones. But Google is the main search engine. GMail is the email. Google Voice is starting to catch on. Even if you don’t have an Android phone, there may be other Android devices (like a Nook) that you pick up. Even if you love Google, you may still have an iPhone.

Who’s going to win? Apple or Google? I say both will win. In some ways, both have already won.

P.S. I do know a couple of iPhone users interested in Google Voice. Anyone with a non-jailbroken iPhone who’s been using the two together for a while willing to share the experience of using the Google Voice mobile page in Safari? Pros and cons?

The other day, I had the opportunity to read a book on her Nook, and it was quite a pleasurable experience. It was a lot better than I thought it would be. I know she prefers clicking the hard button on the side to turn pages. I found I liked turning pages by lightly flicking to the right or left on the touchscreen (after it has dimmed—before it dims, a touch will select a menu item). Even though the Kindle gets a lot more press, the Nook looks a lot better (my wife had some random person on the bus ask her if the Nook was an Apple product) and it supports the ePub format.

What will happen with dedicated eReaders, though? My guess is, unfortunately, they will remain a relatively niche product. I don’t think there is a huge percentage of the populace who reads a novel a day. I think most people read only a little bit at a time. So the eye strain issue of a backlit screen is moot. I don’t agree with people who say “Lots of people stare at backlit screens at work all the time and don’t have eye strain.” I actually know quite a lot of people who do have eye strain from staring at laptop screens. In any case, a lot of laptop users at work are using their laptops to do various small tasks instead of just staring at it reading one long manuscript. And, really, that is how most people will be reading eBooks—a few pages at a time on an iPhone, an Android phone, or an iPad or other touchscreen tablet.

The bright colors and touchscreen appeal will definitely beat out the pragmatic eInk technology on dedicated eReaders… at least for most people. I think my wife can read sometimes two or three novels a day. For her, eInk makes a lot of sense. I don’t read nearly as much as she does, but I think eInk may make sense for me, too.

Tell you what, though—if they can make an eInk screen that is in full color and touchscreen enabled, that would kick some serious electronic book butt.

I should start off by saying that even though this is the best browser to use once you’ve learned how to use it, it is not the easier browser to learn to use. This browser is not intuitive in any way. You will have to read the manual to get the most of your browsing experience. So if you’re the type who usually sees “Find out more about how to use X application” and think “I can skip that. I’ll figure it out on my own,” I would ask that you actually give the tutorial a shot this time.

xScope Advantages

• The first thing that’s great about xScope is that it’s fast. Pages load quickly. They seem to load at a speed a little faster than Steel and a little slower than Opera Mini.
• In other browsers you have to either choose to have it in fullscreen or choose to show the notification bar. I like to have the browser generally fullscreen but also have the option to quickly check the time (the clock is on the notification bar). xScope is great this way, because it starts off fullscreen, but you can press the Menu button and select to have it temporarily windowed. It’ll stay windowed until you choose to make it fullscreen again or until you restart the browser.
• My passwords and cookies are actually remembered. With some other browsers, despite what I indicated in my settings, I had trouble getting the passwords remembered or the website cookies to stay. With xScope, that’s not an issue.
• The browser really is designed with a touchscreen in mind. You can swipe up the address bar if it’s getting in the way, or swipe it down. You can swipe across the toolbar to display the off-screen icons. You can tap once and then quickly tap again and hold and rock your finger back and forth to zoom in and out. After trying double-taps, pinch-to-zoom, and zoom buttons in other browsers, I’m convinced this is actually the best way to do zooming, and, more importantly, it allows me to avoid ever accidentally zooming in or out of a webpage.
• When you click the Back button to go back a page, that page you were previously on loads instantaneously. There is no waiting for the page to reload (hey, default Browser, that’s what a cache is supposed to be for!).

Tab Management
xScope deals with tabs in an elegant and easy-to-use way. First of all, in terms of design, the tabs themselves are big enough to be usable and touchable, but they also don’t take up too much screen real estate.

To open a link in a new background tab (very important, even if you are on a 3G or wireless connection), just press and hold down the link for a second. If you have only one or two tabs already open, you’ll see the link open as a third tab in the background. If you already have three or more tabs open, you’ll see a very quick notification message saying that the tab successfully opened. I like this way of doing things instead of having the tabs crowd each other and get continually smaller… or to get no acknowledgement at all that the tab opened.

To close a tab you’re already focused on, you can just tap the tab itself (don’t need to aim for an X close button). You can also, if the tab you’re looking at has no previous history, just press the Back button to close that focused tab.

To switch between open tabs, you can swipe left or right very quickly and forcefully. This kind of switching wraps around as well (so if you’re on the right-most tab and swipe hard right, you’ll get to the left-most tab). This is very important for reading Google News, because the Google mobile site doesn’t allow you to open links in background tabs, so you’ll get a foreground-loaded tab, and while it’s loading, you can quickly swipe right to get back to the Google News website and browse for other stories to read.

xScope Disadvantages
Well, apart from the fact that its interface is ugly, there are a few other minor issues:

• xScope Lite (the cost-free version) is fully functional as far as I’m concerned. It lacks a few features the paid version has that I consider bloat, but instead of hiding those features, the features are included in the menus… you just get a message to get the paid version if you try to select those menu items. I’d prefer they were hidden, but of course I’m not actually paying any money yet for this great app, so I can’t complain about a tiny bit of nagware.
• Even though xScope is speedy to load up and speedy to use, it’s sometimes very slow to exit. If I exit out of it, I’ll sometimes get half a second of a black screen before my home screen loads up. Not a dealbreaker by any means but just a little lack of polish.
• As I mentioned before, it’s not intuitive. I have found it easier to use now that I’ve learned it, but the learning curve is definitely there.
• There’s no way to turn off images. It is pretty fast already even with images, but the ability to disable image loading would be nice to have, especially if I’m in an area that has poor coverage.
• There seems to be a limit on the number of bookmarks you can have accessible in the start-up page. Odd. I don’t have that many bookmarks myself, but still…

That’s it. Some people may say other browsers have more features, but there is a certain point at which too many features just leaves the browser feeling crowded (try out Dolphin if you don’t believe me). Speed and proper tab management are what matter most to me on a smartphone browser, especially since I am often on a slower connection than I would normally be if I had a wireless broadband connection. Hurray for xScope!

Introduction
Browser
Coco
Dolphin
Opera Mini
Steel
Final Verdict

Introduction

I’ve heard from some Nexus users that they’re perfectly fine with the default Android web browser (called plainly Browser) because 1) their phones are so fast anyway they aren’t looking for another web browser and 2) the latest updates have brought multi-touch (or pinch-to-zoom) to the Browser on Android 2.1.

What about the rest of us Android users? Well, I use a T-Mobile MyTouch 3G (also known as HTC Magic 32b, which has 192 MB of RAM and a 528 MHz processor when it’s clocked to the max), and I can definitely tell you the default Browser on my phone (and probably also the T-Mobile G1) is slow both in terms of general interface responsiveness and in terms of loading pages.

So if you’re fine with Browser, stick with it. Glad it works for you. If, however, you’re looking for an alternative, here are some you may want to explore or avoid.

Browser

Before we begin with the alternatives, actually, let’s take a look at Browser and what you should appreciate in it.

Part of the appeal for me about Browser, at least in theory, is that it doesn’t have too many bells and whistles, and there’s absolutely nothing confusing about the interface. Long-pressing a link brings up a sensible context menu, which allows you to open the link in a new window. Pressing the menu button brings up… the menu, though it’s annoying that you have to click one more time (More) to get to the actual settings.

My favorite option in the settings for Browser is the option to have new windows open in the background, especially since I have experienced Browser to load pages slowly. Unfortunately, Google has recently changed its mobile News site so that long-pressing a link will do absolutely nothing (no context menu), so you have to press the link normally, and it’ll launch a foreground window even if you have specified for new links to open in the background normally.

I use Cyanogen’s rooted Android rom, so this may be something specific to the version of Browser I’m using now. I can’t say I’m a fan of this overview of the currently open windows, mainly because I like to use my left hand to do pretty much all my Android navigation (as opposed to using one hand to hold my phone and the other to push buttons). So it’s a bit of a stretch to get my thumb over to the right to press the close button if I want to close a window.

Coco Browser

I really like the basic interface for Coco, allowing you to see tabs instead of windows and easily select a tab by clicking on it or close a tab by clicking on the close button on a tab. That means fewer steps to manage different webpages (as opposed to clicking Menu, Windows, and then the window’s close button to close a window in Browser). Of course, if you want to manage (well, at least select) the tabs as windows that way, Coco does give you that option, too.

As you can see, most of the settings for Coco are very basic and similar to the stock Browser ones. The one really annoying thing about Coco is that you can’t ever access the address bar. So if you want to go directly to a new page (as opposed to clicking a link to go to a page linked off the old page), you have to open a new tab for that page and then close the old page’s tab. That, for me, was a dealbreaker on Coco. I like tabs as much as the next person, but sometimes I do want to just keep reusing the same tab.

The Android Market is flooded with a ton of task killers and application process managers because most applications don’t actually quit unless (and this I learned only recently) you keep hitting the Back button back to the home screen instead of hitting the Home button to get to home. Coco, when you hit the Back button, prompts you to exit the application. I thought that was nice… not nice enough to keep me on Coco, though.

Dolphin

I don’t really want to include screenshots to cover everything Dolphin does. While Browser and Coco focus on simplicity, Dolphin focuses on including every feature it possibly can into the web browsing experience. You can create little finger gesture shortcuts for closing windows or opening new windows. You have access to various social networking and bookmark management tools. You have tabs. No matter what version of Android you’re using, you have (what I consider the overhyped) pinch-to-zoom.

You can tell even from this screenshot of the menu that Dolphin is packed with a lot of what could be confusing or heaven-sent options, depending on what kind of user you are. Incidentally, pressing the actual Menu button doesn’t bring up the menu. You have to press Dolphin’s own virtual menu button to get that menu up.

If things aren’t confusing enough, the Settings part of Dolphin has two sections. You scroll all the way through the first set of settings, and then click the last link and you get another long second list of settings to scroll through. It’s in that second list that you can find how to change the home webpage.

Even though Dolphin has visible (but better-looking than Coco) tabs, it also has a nice way to manage windows. You can also easily switch between windows by swiping really hard to the left or right. That is very handy.

Some people complain about the ads, but the ads aren’t too intrusive. You see little tiny text-based ads when you bring up the start page, and the default home page (which you can change) also has ads on it. Clearly a lot of work went into this browser, so it makes sense they’d need some funding to keep this project going. There’s also a pay-for version in the Android Market that removes the ads.

Ultimately, though Dolphin is a good browser, I just found its interface too clunky for my tastes. I can understand how a power user (particularly one who uses mouse gestures on a desktop web browser, or one who’s really attached to pinch-to-zoom) would love this web browser, though.

Opera Mini

I tried Opera Mini 4.2 when that was around, and it was pretty much unusable on my phone, since mine is a touchscreen-driven phone (no hard QWERTY keyboard). Opera Mini 5 (in beta as of this writing but still available in the Android Market) is a huge improvement over 4.2. It does have its drawbacks, though.

Here’s one major one—it doesn’t really seem to be integrated with Android… at all.

1. The app needs at least a few seconds to load, and it’s slow enough that I had time to take this screenshot while it was loading… and, yes, that progress bar appears every time you load Opera Mini.
2. When you’re in Opera, if you press the Dialer button, nothing happens. It’s like you’re trapped in Opera unless you decide to leave. Want to make a phone call? You’ve got to press the Back or Home button first. There’s no temporary vacation away from Opera.
3. Here’s the worst part: there isn’t a way to make Opera your default browser. Usually, after you install a new browser, when you click on a link or do a search from the search widget, Android will prompt you about which browser to choose and then allow you the option to make that the default. Opera doesn’t do that, even if you go to Settings > Applications > Manage Applications and clear defaults from the current default browser. So if you really like Opera Mini, tough luck. It can’t be your default browser. You’ll have to explicitly launch it every time you want to use it.

The Opera interface is really easy to use. You have an address bar you can type into, a Google search bar you can type into, back/forward buttons, tab management, and settings. Long-pressing on a link gives you two simple options—to open in a new tab or select the text.

The settings are very visually oriented and not confusing at all. Opera Link, if you choose to use it, allows you to sync your bookmarks to a desktop Opera installation.

Instead of bringing you to a separate screen to manage tabs, Opera just pops up a tiny thumbnail gallery at the bottom. Apart from the simple and easy-to-use interface, Opera’s main advantage is speed. It is way faster than any of the other browsers, because Opera actually loads the pages on its own servers and then compresses the images and text before sending it to your phone. So even if I’m on the Edge network instead of 3G, and I have only one or two bars on my phone’s signal, I can browse webpages speedily in Opera Mini 5. Loading windows in the background (as I do with Browser) is wholly unnecessary.

Opera starts off with a larger view of the webpage. The tap-to-zoom is inelegant (no animation whatsoever) but is extremely practical. It gets you to exactly what you need to see. As I’ve mentioned before, I think pinch-to-zoom is overrated.

Opera has some weird problems that I hope get worked out in future versions:

• The font rendering is terrible.
• The Google search icon is pixelated.
• You have to double-tap the close button on tabs to get them to close.
• So-called Fullscreen mode just drops the address bar at the top and menu bar at the bottom. The notification bar at the top is still there. And Opera without the menu bar at the bottom is crippled (you have to press Menu to get it to appear again).

Steel

Steel would be my absolutely favorite web browser on Android, if it just worked the way it was supposed to. First, let me describe how it works in theory.

What I’m showing here is what an actual webpage looks like when it’s loaded. However, when you first launch Steel, all you’ll see is a blank page. You can press Menu to get to the settings, though.

The settings in Steel are quite nice. You can have Steel load a blank page, your home page, or the last page you were looking at. You can easily change the user agent from Android to desktop or iPhone. Fullscreen mode is actually fullscreen (unlike Opera’s fake fullscreen). You can also have the controls (the dark gray bars on the top and bottom) disappear into a little bubble in the bottom-right corner after five seconds. (Tap the bubble to get the controls to reappear.)

Steel is a browser that is fully designed for touchscreens. As with Dolphin, you can swipe hard left or hard right to switch to the window to the left or to the window to the right. If you want to open a link in a new window, you long-press and right after the context menu comes up, instead of selecting one of the options, you just let go of the screen immediately.

Okay. That’s at least how it’s supposed to work. In actual practice, though, I had to give up on Steel because it kept crashing (force closing) every time I closed the left-most window, it was too sensitive to touch (if I was holding down a blank space for even two moments, the zoom controls would come up), it would forget my cookies for various sites or not prompt me to remember passwords for them (so I’d have to log in with username and password all over again), and it would slow down considerably if I had four or five windows open at once.

Final Verdict

Well, I can’t make a final verdict for you, but what I ended up doing was keeping Browser as the default for the search widget, and then using Opera Mini if I want to browse for anything else.

I hope you’ve found this helpful!

Screenshots for this were taken using Ubuntu and the Android SDK as per the instructions in this tutorial

Linux had a few good opportunities to succeed, but flubbed on the execution:

1. OLPC. When I heard about the One Laptop Per Child project, I got giddy. It was marketed as the $100 laptop. It was going to be durable. It was going to use Linux. It was going to help kids in developing countries learn. If that had been what really happened, Linux would have really taken off, at least in certain demographic segments of the world. What really happened? Well, the laptop was nowhere near $100. It was more like $200. And if rich folks wanted them, they had to pay $400 ($200 to get one, $200 to give one). It also was a pretty ugly laptop, with an extremely crippled version of Linux.
2. Dell. When Dell started up its Idea Storm section, it probably had no idea the section would be bombarded by Linux users demanding Dell start offering Linux preinstalled. Well, Dell half-heartedly gave in and offered a couple of select models with Ubuntu preinstalled. This half-hearted effort doomed the new venture to failure. Dell hid Ubuntu away so no one could see it on their website without a direct link or clever Google searching. Dell priced the Ubuntu laptops more than spec-equivalent Windows laptops. Dell “recommended” Windows on all the Ubuntu laptop pages (it still does). Dell still used Linux-unfriendly hardware (Broadcom, anyone?). To sum up, Dell was not invested in really selling Linux preinstalled. It just wanted to sort of, kind of appease the Linux community (most of whom continue to buy the cheaper Windows-preinstalled laptops and then install Linux for themselves).
3. Netbooks. I love the idea of netbooks. The execution was terrible, though. They were not heavily advertised. Early netbooks had 512 MB of RAM and 4 GB SSD drives with 7″ screens. The battery life was poor. The keyboards were cramped. The screen resolution was practically non-existent. Worse yet, all the OEMs included crippled versions of Linux… Linpus Linux Lite, Xandros… installing software became in reality the nightmare that Linux haters often misrepresent it to be. It would be like having apps for the iPhone without an App Store. Yes, you could install a regular Linux version yourself, but that’s not what the everyday consumer is going to do. Microsoft slammed the years-familiar XP down on netbooks, and—suffering from a bad implementation and no marketing or advocacy from OEMs—Linux on netbooks floundered.
4. Android. In many ways, Android is actually a success. But it is not the success it could have been. When people were saying various Android phones could be the next “iPhone killer,” I thought, Hey, maybe they could be. We’ll see. I wasn’t surprised to see that the G1 did not kill the iPhone, the MyTouch didn’t kill the iPhone, the Hero didn’t kill the iPhone, nor did the Droid, nor did the Nexus One. I have a MyTouch 3G with Android, and I love my phone. I understand very well why it didn’t kill the iPhone, though. Apple understands how to make an excellent user experience, and Google doesn’t. That’s the bottom line. I’m not an Apple fanboy. I actually disagree with a lot of the design decisions Apple makes. What I don’t dispute is that Apple has a vision. Every decision, whether I agree with it or not, has a rationale that makes sense. Yes, there are pros and cons, and Apple weighed them and decided the pros outweighed the cons. With Android, though, and with various HTC phones using Android, I see various bad interface implementations that have no pros at all. I just don’t see anyone properly testing these things. For example, on the MyTouch and the Nexus, the speaker is on the back of the phone. Why? On some of the Android text dialogues, you have to tap into the text field (even if you have no hard keyboard) to get the onscreen keyboard to appear (shouldn’t it appear automatically if the text field is in focus?). Those are just a couple of examples.

Just yesterday, Steve Jobs announced the iPad to much ridicule. People made fun of the name. People said it would be useless without Flash, a USB port, without a front-facing camera, without multi-tasking. They called it an oversized iPhone. They said the 4:3 aspect ratio wouldn’t be good for movies. The LED screen wouldn’t be good for reading in sunlight or for long periods of time.

I kind of liked it. I wasn’t overwhelmed by it. I wasn’t drooling. But I can see the appeal. It looks like a slick device, and it’s priced a lot lower than people thought it would be (most of the speculation saw it between $700 and $1000). If it’s a standalone device (doesn’t need to hook up or sync to a Windows or OS X computer with iTunes), I might consider it.

I would be curious to see if any OEM is going to step up to the plate here, though, and give Linux a real chance. I doubt it. It would be quite simple, though. Create a tablet just like the iPad (has to include proper multi-touch, though… no backing out for fear of so-called patent infringement, Google). Run a Linux-based operating system that is mainly open source (but can have some proprietary programs on it). Include multi-tasking. Include a proper software repository. Use a regular hard drive instead of SSD drive. Include USB ports. Have better screen resolution or a widescreen aspect ratio. Then price it just a little below the iPad… oh, and give it a proper name… one people won’t make fun of.

How simple is that? Will it happen? Probably not. A bunch of iPad imitators will pop around, sure. They’ll each have serious flaws, though. Many will lack multi-touch. Most will be too bulky. Some won’t have a sensible user interface. Some will be too expensive. Then I can tack it on as yet another way Linux has failed in the consumer space.

Mark Shuttleworth, if you’re reading this, it’s about time you realized Bug #1 gets fixed once you create a full and unified software-hardware user experience. Hoards of Windows users aren’t going to download the Ubuntu .iso, set their BIOSes to boot from CD, repartition their hard drives, install Ubuntu, and then troubleshoot hardware compatibility problems. You (or someone with your savvy and financial resources) need to be the open source Steve Jobs if Linux is going to succeed in the consumer space.

Well, it’s been almost four months, and I have to say that my general impression hasn’t changed much. I can sum it up as generally positive with a few annoying glitches. If you are a part of the Apple ecosystem already, the iPhone is a better choice. But if you are a Linux user or already caught up in the Google ecosystem, an Android phone is a much better choice. A lot of other Android phones have had more hype (Hero, Droid). The MyTouch is a good phone, though. If I actually liked Sprint, I would have waited for the Hero. And if I actually wanted a boxy-looking phone with a “real” keyboard, I’d have waited for the Droid.

Here are the annoying glitches that have bugged me the most:

• Every web browser for Android has a serious flaw. Ultimately, I’m willing to settle for the flaws in Browser over the flaws in the other ones (Steel, Dolphin, Opera, etc.).
• The Facebook app is basically good, but when you click on a picture thumbnail, it doesn’t enlarge the picture within the Facebook app. Instead, it launches the Browser app to view the picture. Lame.
• After the whole cease-and-desist fiasco, I wanted to support Cyanogen for making a Google-compliant fully legal rooted (i.e., jailbroken) ROM, so I’ve been using Cyanogen recently. Unfortunately, the performance has been spotty. Sometimes it’s super-speedy, and sometimes it’s super-laggy. I may end up giving DWang’s ROM a go again, even though it’s not technically legal (it’s in the spirit of the law but not the letter—apparently Google cares very much about the letter, though).
• Google Voice is a great service. The Google Voice Android app, however, is buggy as all hell. Sometimes it crashes. Sometimes it’ll randomly duplicate SMS messages if I write the message in landscape (instead of portrait) mode.
• This doesn’t really bother me any more. If you are thinking of getting a MyTouch, though, you should know this: the touchscreen interface takes getting used to. Unlike the iPhone, light swipes are not recognized. You need to press your finger on the screen when you swipe.
• With the latest versions of Android, there is no way to disable the camera sound (which is extremely loud). I had to install an app called Sound Manager in order to silence it.

That’s about it.

What has been the good stuff?

• Opening links in background windows (except the Google recently changed its Google News website so that you cannot open links in background windows—other sites work fine with it, though).
• Good Google Voice integration.
• Ability to turn any song into a ringtone without special software is great. Right now the Noisettes’ “Wild Young Hearts” is my ringtone.
• Ability to send unwanted calls straight to voicemail through the phone and to just block them altogether with Google Voice is invaluable.
• USB tethering is even better than Wifi tethering. You just plug it in and Ubuntu automatically starts using the connection. No need to select anything or change a setting.

In the end, though, a phone is a phone. It makes calls. It receives calls. I can check my email and look up something quick on the web. There are subtle nuances that will differentiate Symbian from WebOS and Windows Mobile from the iPhone OS X and all that from Android. SmartPhones all pretty much do the same thing, though.

With some recent updates to Donut from Cupcake (or maybe even some backported Eclair updates in the Cyanogen rooted mod—not sure), that option has somehow disappeared from the camera settings. Frustrating. The only thing worse than lacking basic functionality in an interface is taking away fuctionality that had previously been there.

I did quite a bit of Google searching to find out if anyone else had this problem. Basically most people either didn’t have the problem or had no solution to it. One person suggested an app called Snap Photo. I installed the app, saw there was an option to disable the clicking shutter noise, but the noise was still there even when I selected that option. Another person suggested turning off the phone volume, taking the picture, and then turning the volume back up. An effective workaround but quite a bit of hassle, don’t you think?

After browsing through quite a few options in the Android Market, I finally stumbled upon an app called simply Sound Manager. It was perfect. It allows you to fine-tune the volume so you can keep the ringer, media, and other volumes at normal levels and then turn off the system volume, which is responsible for that annoying click noise. There you have it: Sound Manager.

So after Cyanogen released a stable version of the Google-compliant rooted Android mod, I wanted to give it a shot. It isn’t quite as speedy as Dwang’s mod, but it’s usable, and I like that no lawsuit is going to suddenly bring it to an end (it has long-term sustainability).

So I then went on a quest to find a good theme for this new version of Cyanogen’s mod. I tried out a Ubuntu theme and a Hero theme, and I looked at a bunch of other themes that appeared to be too gaudy for me.

Finally, I stumbled upon the Little Big Planet theme. I remember my wife playing this game on the PS3. At the time I thought the little sack guy was cute in a demented sort of way. So I flashed the theme, and I like it. For those of you who are curious (and who do not want to create a login for the XDA Developers forum just to see screenshots), here is what the theme icons look like:

I think I can live with this theme for a while.