Tag: android

The State of the Slate: Today’s iPad and Tomorrow’s Tablets

The iPad created a new class of computing devices and a new way of interacting with technology. It seems like this ambitious device means something different to just about every segment of the technology world: Old Media publishers herald the device as their salvation from death at the hands of the Web. Open software advocates balk at its controlled app platform as a regression for things like rich web applications and open standards. Tech pundits label it a device which prioritizes passive consumption of content over production and collaboration. Customers complain about the $500 starting price — and then buy over 15 million of them in under a year. (This quarter, Apple is on track to sell more iPads than Macs.)

I took the plunge and bought an iPad last September to see what all the fuss was about. I have to say that I don’t think any of the popular perspectives effectively mirror my experience. Things are about to change very quickly in this new space, and I think this is the appropriate time at which to reflect on its current state and potential in the future.

Continue reading The State of the Slate: Today’s iPad and Tomorrow’s Tablets

Jan. 5 CES Highlights & Analysis : Android Goes Slate, Windows Goes ARM, and an iPad 2 Tease

It’s that time again: CES, the annual consumer electronics convention in Las Vegas where companies show off their gadget game plans for the upcoming year.

This is usually the biggest time of year for gadget news – tech blogs and Twitter feeds are overflowing with information, which can be too much for even those paying attention all day. These are the most significant things I noticed from today’s announcements:

LTE smartphones barrel forward while American carriers slap a “4G!” sticker on their 3G networks

Phone after phone gets announced, almost every one of them having the same specs: 4.3″ display, Android 2.3 “Gingerbread,” dual-core 1GHz ARM CPUs, front- and back-facing cameras. The only development here over that of one year ago is the extra CPU core, really- HTC’s EVO 4G and Incredible of yesteryear are almost identical to their HTC ThunderBolt, which only adds LTE to the mix.

Sadly, this year’s announcement of 4G phones doesn’t live up to the hype being generated by the phone carriers. The reason: most of the phones marketed as “4G” run HSPA+, which is actually just the fastest revision of current 3G GSM technology. The real 4G phones have converged on the LTE standard, except for Sprint, which bet its chips on WiMax to get a years’ head start. AT&T today followed T-Mobile’s lead in deceptively rebranding their existing network as 4G. The reason? Their own LTE 4G transition won’t be complete until 2013, while Verizon’s antennae lit up in December 2010. If you’re buying a phone in 2011, take the time to find out if it can even take advantage of these next-generation networks that offer incredible speed boosts.
Sources:

Legitimized by consumers as a new device format, slates turn to Android

Last year, manufacturers flooded CES with slate devices in anticipations of the rumored Apple iPad. Without exception, they all sucked, being low-cost devices with Android 1.5 or 2.0 haphazardly tacked on without any considerations to changing a UI designed for 3.5″ phone screens.

This year, everyone knows the iPad is a bombshell at around 10 Million sold, and wants to get in on an obvious growth market. Google today announced the Tablet-specific version of Android 3.0, “Honeycomb”:

[youtube=http://www.youtube.com/watch?v=hPUGNCIozp0&w=640&h=385]

(Stay tuned to ZekeWeeks.com or @ZekeWeeks for my in-depth reactions to Android 3.0 Honeycomb – to be posted soon.)

A possible iPad 2 tease on the show floor

Dexim's purported iPad 2 metal mockup
image credit: Engadget / AOL - click to see their article

Engadget’s bloggers were trying to fit their iPad into a vendor’s unique iPad case on the show floor when they were told it wouldn’t fit, as it was designed for the next iPad. Better yet- the case included a metal mockup with the supposed form for the iPad 2. Is it real, or just a clever PR exploitation of the Apple rumor mill? Read Engadget’s great post about it all, including a photo gallery, here.

Microsoft takes desktop Windows to the mobile ARM platform, while Nvidia takes ARM to the Desktop format

After enjoying moderate success from the Atom-powered netbook boom of 2008-9, Microsoft has obviously read the tea leaves that all the cool kids are building their devices on ARM-based System-on-a-Chip (SoC) silicon, instead of the traditional IBM PC setup that’s been shrunk down to miniature form on netbooks. In an effort to make Windows avoid complete irrelevance take advantage of current ARM innovations, Microsoft has announced that the next version of Windows will run on ARM in addition to x86/AMD64. But all Windows executables will need new ARM-compatible versions, unless Microsoft has a Rosetta-esque dynamic translator up its sleeve. That Windows would even consider this route on consumer devices is interesting, as Windows apps are have been forwards compatible since the 1980s. Perhaps it’s a telling sign of Windows’ ability to compete in the future. (And perhaps I’m looking to far into this.)

On the other side of this coin, chipset maker Nvidia announced “Project Denver,” their adaptation of the mobile ARM architecture to high-power desktops and servers. (Jon Stokes writes more about Project Denver at Ars Technica.)

Yet again, a big web property’s new feature makes independent developers’ products irrelevant; This time, it’s Twitter

This isn’t really CES news, but it still got buried in all the CES coverage: TechCrunch secured confirmation on reports that Twitter will release a first-party Mac application during tomorrow’s launch of the Mac App Store. If it’s free, and even more so if it’s ad-free, third party developers are not gonna be happy (though one could argue that they have ample opportunities to innovate beyond “cookie cutter” Twitter clients.)

So there you have it. Tons of stuff today! Stick around on ZekeWeeks.com or just follow me on Twitter, as I’m sure to post on anything of major significance that emerges amongst the thousands of announcements made at CES. Coming up next is my in-depth analysis of what is to come of Honeycomb, Google’s slate-specific version of Android OS.

My Solution for the Android Bloatware Problem

City ID software soliciting a paid subscription
City ID, a non-removable app preinstalled on my HTC Incredible by Verizon to get more money from me. They even start off with an unannounced trial of the functionality and hold it hostage 2 weeks later unless you pay up.

Note: Skimmers should definitely skip my overtures and get straight to my recommendations at the bottom of this post.

A lot of concern has cropped up regarding “bloatware” in the most recent batch of smartphones running Android. There are really two sources of complaints in this area:

  1. Custom User Interface skins put on top of the stock Android OS by the manufacturer.
    These skins take a generic, manufacturer-agnostic OS and create an experience unique to an individual manufacturer’s devices. Manufacturers seem to experiment endlessly with these custom UIs, often revising them with each new generation of device. They vary a lot in quality, but in turn also create more options for customers to choose the device best tailored to fit their own personal preferences. (Some will decry the existence of any custom UI, but I am in love with the time-tested HTC Sense UI, and moreover think that an “open” platform should allow for such innovations.) But it’s now impossible to buy a high-end Android phone in the United States without one of these custom UIs. With Google’s removal of their Nexus One phone from the consumer market, there are few examples of phones offering the pure “Google experience.”
  2. Additional “bloatware” programs pre-loaded onto phones by carriers to make a quick buck.
    Just like many new Windows PCs, carriers now compensate for their ever-decreasing margins on device sales by loading programs onto their phones for the purpose of generating more revenue, often without regard for the quality of the customer’s experience with the end product. One phone comes with a non-removable copy of Avatar; another has the search set to Bing by default and doesn’t allow owners to change to another service; AT&T doesn’t allow the loading of programs outside the Android Marketplace; and yet others build basic caller ID or visual voicemail apps and tack disproportionate monthly fees onto the bill for their use.

I’m not surprised or discouraged to see this come up as an issue as the Android OS matures. In fact, Android works this way by design. Android would not have existed as a product if it weren’t for the support of the Open Handset Alliance, a huge consortium of carriers, manufacturers and developers who stood to benefit from such an open platform. Back in 2007, the iPhone turned the smartphone status quo upside down, and did so by taking almost all the power away from the carrier with a vertically integrated product of uniform hardware and software. Any company wishing to make money in Apple’s new market, they had to first cede the final say on all matters to Apple, who in turn prioritized the quality of the user experience above all else. In many ways, Android only became successful because it gave carriers the opportunity to re-prioritize profits over quality products and services.

This isn’t to say that Android is doomed to a future of bloatware and terrible UX. Indeed, we’re seeing rather textbook examples of differentiation in a free market. Android is the best platform for differentiating devices for different preferences and price points. And anyone who oversteps the bounds of what a customer is willing to buy, they won’t succeed. And on top of these economic norms, Android’s open nature and fast release cycle makes it the most accessible mobile OS for innovators throughout the platform, from app developers, to service providers, to device manufacturers.

But at the same time, it’s clear that no American carrier sees economic benefit in selling a “pure” Android phone. Manufacturer-controlled phones from RIM and Apple are seamless integrations of hardware and software, and even Microsoft is asserting more control over the process with Windows Phone 7. With rumors of an imminent end to the iPhone’s exclusivity, it’s possible that carriers could just see Android as a good lower-end option below “premium” offerings on other OSes.

But I think this can be easily changed to keep Android’s momentum working in a positive direction without making sacrifices to openness, profits, or much else. Here’s how:

  1. Change the “Google logo” terms to put the customer’s needs first again.
    Android itself is totally open source and free, but you have to follow some extra rules to get the “with Google” logo and access to Google’s apps, including the Android Marketplace app store. Right now those rules aren’t very demanding, but Google could definitely insist that extra OEM/Carrier things on top of stock Android be removable by the end user. (They could even go as far as to ban custom UIs or bloatware, but I think it wouldn’t fit Android’s open nature, and would be a losing move towards competing with Apple’s business model.) “But what about the lost carrier revenue?” That’s where step #2 comes in:
  2. Give carriers a share of Google’s 30% cut on app sales.
    This gives them an incentive to make more pure “Google logo” devices over crippled alternatives. As carriers worry more and more about becoming generic service providers of wholesale data bits, this gives them a significant new revenue stream that actually rewards them for making the devices their customers really want. “But the Android Marketplace is mostly free apps, this isn’t Apple’s app store…” That’s true, but sacrifices don’t need to be made there, either:
  3. Charge developers an annual fee for the Android Marketplace to encourage paid apps, but protect developers’ existing freedoms
    Apple charges each developer $99 per year to develop and sell their applications in their store, and the only alternative is through jailbreaking. Android’s Marketplace is more financially accessible, and has a lot more free apps. To convince carriers that a Marketplace revenue share is attractive, they would need to change the Marketplace’s composure to a more revenue-driven approach. But the existing community of free app developers should also be accommodated for – I envision creating even more freedom for developers to use alternative distribution methods, first by forbidding AT&T-like restrictions on outside applications, and even – this is probably too optimistic – making root/super user access an easy opt-in setting on every phone for geeks who know what they’re doing.

I have no experience in the telecom industry, and I bet the folks in charge of Android at Google know a lot better than I, but I think something like this would be a logical direction to take as Android moves to new heights of popularity. I wonder especially about revenue sharing in the Marketplace when the carriers are going to the lengths of crippling their own devices in order to compensate for diminishing margins on unit sales.

Apple’s iOS Development Manifesto: Are They Afraid of Android?

This caught my eye- Apple has released a new video featuring the full gamut of iPhone and iPad application developers, from tiny shops to tech startups to media giants. While I think it’s overall not too remarkable – merely an ad presenting the strengths of Apple’s development platform for mobile devices – I do think it very clearly presents Apple’s approach to the mobile market.

[youtube=http://www.youtube.com/watch?v=UER_yQGXyV8&w=640&h=385]

Seeing this video makes me wonder about Apple’s competitive strategy in the quickly evolving mobile device markets. In 2007, they forced the lazy rulers of the cellphone market to start innovating again – and now they’ve finally caught up and started producing high-quality phones, some of whose features apply to many niches better than the “one-size-fits-all” iPhone. Though not #1 in smartphone share, iOS (previously called iPhone OS) certainly dominates among those using their phones for more than SMS and e-mail. But has domination ever been Apple’s strategy? Since Jobs’ return to Apple, the company has shown no ambition to kill the competition; I think they in fact benefit from having competing products around to make the case of Apple products’ superiority. And while the iPhone and iPod certainly lead in their markets, OS X certainly doesn’t – and the three use Apple’s same approach to producing highly-polished combinations of hardware and software.

I’ve maintained that 2010 would be the year of the Android phone, and I think that so far things are turning out that way. Not in terms of an “iPhone killer,” but in terms of a serious competitor. The growth of Android devices, market share, and applications have all exploded, and the Android Marketplace is quickly evolving from a ragtag group of ugly tech utilities to genuinely amazing ones that contend with some of the best iPhone apps. I wonder how Apple views Android now, especially in the light of this video, which takes several shots at perceived downsides to the Android platform. It’s certainly true that today, iOS delivers the biggest return on investment for development work. But where will things go in the future? There are some critical differences in the platforms which affect their potential:

  • Apple’s AT&T exclusivity in the US
  • Approach to usability: Apple picks form & ease of use; Android says, “why not have an annoying menu button if it gives you access to a bunch more features?”
  • Android’s double-edged differentiation sword: can better target various niches, but also introduces fragmentation and compatibility concerns for developers
  • OEM and Developer innovation: On Android, new features can be created just about anywhere, anytime; iOS waits for others to innovate and then introduces a way to “do it right”

I don’t think most of these things are “X is better than Y” values but inherent differences in the appeal of different platforms. As an owner of both kinds of devices, I think we’re going to see Android push smartphone penetration to all kinds of new market segments, and be the new platform for innovation. I see iOS as a major player for the long term, though probably not hanging on to its current dominance of high-end smartphones. There’s plenty of room for both moving ahead, and the only thing that’s certain is that everyone gets more options in their search for the device that best meets their needs.

HTC Droid Incredible first impressions

My HTC Incredible came in the mail today from Verizon. After ripping the package open like a kid on Christmas, I ran into the good and bad of the device very quickly. I don’t have time to do a full writeup on the Incredible right now, but here are my impressions from the first few hours:

(for some perspective, I have been on an original iPhone for two and a half years, and I tested the Motorola Droid for a month after its release before deciding it wasn’t for me.)

Pro

  • HTC’s Sense UI is nothing short of amazing. I wasn’t surprised to see Android have a clunky default UI, seeing as Google is such an engineering-centric company, but HTC really put a lot of thought into streamlining the whole user experience. Sense has a much better keyboard and autocorrection system, which has me typing at almost the speed I type on my iPhone, on which I’ve had two and a half years’ practice. Also, the UI is fully multi-touch, and does so very well.
  • Performance wise, this phone screams. Nothing seems to choke it up.
  • I’m still getting used to the “optical trackball” at the bottom of the phone. I want to use it like an inertial scroll, similar to a finger swipe on the screen. It’s a pain to try and scroll with just the nub of my thumb, but once I swipe the whole length of my finger across the trackpad, it becomes a lot more useful.
  • Speaker quality is very good for both the earpiece and the speakerphone.
  • So far I am impressed with the quality of the camera and its dual-LED flash. The autofocus works very well. I’m disturbed that my phone captures images at 8 megapixels while my high-end point-and-shoot has six.
  • Complaints about the Incredible’s quality of materials are highly exaggerated. I prefer metal phones myself, but this hardware is very solid and have no doubts that it’ll last me through a 2-year contract. (I couldn’t say the same about the Motorola Droid, which had a loosely seated headphone jack and battery cover that was constantly falling off.) The soft touch plastic back feels great, and its unique angular design on the back is a lot more subdued than it looks in pictures- once you feel how thin the device is, it’s a lot less of a problem.
  • Likewise with the display- people say AMOLED displays like those on the Incredible and Nexus One are terrible in sunlight. Yes, it is not very good, but it only becomes a serious problem with the sun beating straight down on it from overhead. (Want a display that deserves a bad rap? Try a Palm IIIc.)
  • Verizon sent a free 2GB microSD card in the box that wasn’t advertised in the pre-order contents. My guess is that this is Verizon’s quick fix for existing compatibility issues for apps that don’t recognize the device’s 8GB of internal flash memory, which is a first for an Android device. Yes, it’s small, but it’s free and unexpected. My bet is that these phones will start coming with microSD cards preinstalled.

Con

  • The display is quite good, but doesn’t blow me away quite like the Motorola Droid did.
  • Cell reception is noticeably worse than that of the Motorola Droid. I haven’t tested this enough to know if it’s a serious issue or not.
  • The Incredible comes loaded with HTC’s version of Flash Light, which works with some stuff and doesn’t work with other stuff. It’s an imperfect solution, and becoming irrelevant as Apple forces the web towards HTML5, but Android 2.2 will have full-powered Flash anyways.
  • The USB port on the device plugs in on the bottom left side in portrait orientation- right where you want your left palm to rest while typing with both thumbs in portrait orientation. You can mangle your fingers around it in an effort to avoid it, but basically you’re going to want to use this puppy in landscape mode all the time while charging.
  • There are without a doubt some growing pains for a brand new device launching just today on Verizon. My data connection didn’t work at first, and Verizon’s technical rep told me it was likely a problem with HTC and Verizon’s initial network setup for this phone. They got it working for me eventually. (The problem was server-end.) Also, some things that could be fixed in a firmware update include an oversensitive ambient light sensor – it seems to make tiny adjustments when lighting conditions barely change – and navigation button LEDs that occasionally turn off when they shouldn’t.
  • Motorola preloaded a lot more interesting ringtones on the Droid than HTC did on this phone. That’s a matter of taste, but I found myself rushing to make my own ringtone ASAP on this thing.

So basically, this phone addresses almost all of the concerns that kept me from keeping the Motorola Droid. Sense UI is a joy to use, performance is increased, and the build quality seems much more solid to me (albeit not metal). I feel like I’m much more likely to choose to keep this and move my contract over to Verizon. The only holdout I have in my mind as of now is the quality of cell reception, which I’ll have to test some more outside of my signal-killing brick house.

iPhone Dual Boot with Android Working

David Wong, better known as “planetbeing” of the iPhone Dev Team which produces jailbreak after jailbreak, uploaded this video detailing his rather mature port of Android OS to dual boot natively on the original iPhone:

[youtube=http://www.youtube.com/watch?v=5yO2KQHkt4A&w=480&h=385]

Video link

This port, while not mature enough for most people to start relying upon it for their everyday use, is an incredible achievement that has the potential to tangibly change the face of tomorrow’s smartphone market.

Don’t get me wrong: dual booting iPhone OS and Android offers pretty much nothing to the everyday consumer. Even for gadget geeks like myself, its added utility will be nothing more than a cheap trick for showing  people 2 OSes, 1 Phone. (Sorry.) But what makes this important is that soon, developers will only have to have one device to develop for both iPhone and Android platforms. And many developers already own the device needed to do so.

This might possibly be a catalyst for even more development on the Android platform, as it will become available to millions of devices that are already in users’ hands. If it catches on, I think we’ll start seeing a much more mature Android Marketplace and a lot more small shops developing dual-platform applications.

This still has a good ways to go before it’s a useful solution:

  • This port isn’t of the recent Android 2.0 or even 2.1 releases- rather a 9-month old one.
  • It only runs on the original iPhone, with a small user base. planetbeing says porting to the much more popular 3G should be easier, and the 3GS with more work.
  • It isn’t a fully-customized port; button functions have funky mappings and it needs to be better integrated to the hardware to become useful.

Overall, planetbeing has done an incredibly impressive job with his port, and I’m surprised this was even remotely possible, much less such a functional port.

planetbeing has hosted the initial pre-built images and source here. Check out his post for more information, and give him a donation if you’re someone who stands to find this port useful.

What iPhone OS 4 means to everyone

Today Apple announced their latest revision to iPhone OS, the mobile computing platform behind the iPhone, iPod Touch, and iPad. iPhone OS is running on over 85 million devices, so it’s a pretty big deal. I don’t want to waste my breath repeating every announced feature, so I’ll just refer you over to Engadget’s excellent summary of it all.

This will be the fourth major release in four years for Apple. But for the first time, this release seems to be more evolutionary than revolutionary. Overall, I think Apple is trying to keep up in feature parity with this year’s huge new threat from Android devices. That competition isn’t necessarily a bad thing; Apple has a long history of waiting to enter a market and then turn it upside down and shake all the customers out of the competition’s pockets. (See: iPod, iPhone, possibly iPad.) But I think OS 4 in specific brings up some new issues for everyone who has a reason to care about mobile computing.

Innovators & Developers

What worries me most is Apple’s approach to allowing background tasks to run. Instead of implementing real multitasking in the same way desktop computers do, where every program stays running and can request CPU resources at any time, they have created seven services to allow specific actions to run in the background: audio, VoIP, geolocation, push notifications, local notifications, task completion, and fast app switching (which isn’t really a service, but the new behavior of “sleeping” rather than quitting an application.) Yes, this allows for a lot more functionality in apps while addressing a lot of the problems inherent in allowing multitasking on a mobile device. But why it’s interesting, and in my opinion not so great, is because it limits ways developers can innovate and make the next “killer app.” It’s like Apple said, “What can’t people do without multitasking?” (Or more likely, “What is Android doing now that we can’t?”) and then put out specific fixes for those existing use cases. Yes, users will soon be able to leave Pandora or Skype running in the background. But guess what? You don’t work for Pandora or Skype, and you probably don’t want to compete with them. This is a stop-gap reaction to current iPhone deficiencies instead of a new platform upon which innovators can make the Next Big Thing. I’m not saying iPhone OS multitasking itself is a bad feature; I’m saying that the platform is restricted to moving in directions chosen by Apple instead of letting developers take the helm. My bet is that we’ll see killer apps continue to be more functional on Android before they get “backported” to iPhone versions.

Another disturbing revelation is Apple’s banning of tools that allow applications to be developed with other platforms and then cross-compiled to run as native iPhone apps. MonoTouch allows iPhone apps to be written in .NET, and later this month Flash CS5 will add iPhone support as well. The new terms:

3.3.1 — Applications may only use Documented APIs in the manner prescribed by Apple and must not use or call any private APIs. Applications must be originally written in Objective-C, C, C++, or JavaScript as executed by the iPhone OS WebKit engine, and only code written in C, C++, and Objective-C may compile and directly link against the Documented APIs (e.g., Applications that link to Documented APIs through an intermediary translation or compatibility layer or tool are prohibited).

I believe this crosses the line and is textbook anticompetitive behavior. It’s one thing to say your OS will only run Objective-C apps. It’s another thing to say that your Objective-C can’t have been created by certain tools. I’ll leave it at that because John Gruber already has a thorough analysis of this issue.

Consumers

Customers can look forward to yet another great evolution in one of the best – if not the best – mobile platforms. The new features keep up to par with all the new Android phones while still beating them on ease of use. If Apple’s track record continues this year, there will be a whole lot more for consumers to be excited about when new iPhones are announced this summer.

The Competition

  • Android (Google): Android’s key differentiators are gone, except for Google integration and the open development model. Google had better hope the iPhone stays exclusive to AT&T. If Android doesn’t keep up on performance and improve the user experience, fighting the iPhone will get a lot harder this year. Potential game changer: open app marketplace yields a killer app unavailable on the iPhone.
  • Windows Phone 7: iPhone OS adds better and better enterprise features with every release. Trying to convert to the same business model as the iPhone is a fatal mistake. Microsoft needs to kill WinMo 7 and buy RIM or Palm if they have any will to survive in this space.

Cell Phone Carriers

Skype has an amazing iPhone app. It will soon be running all the time and will let people make and receive unlimited calls for free. AT&T has already changed its mind and decided to allow unlimited VoIP traffic on their cellular data networks. The days of bundling tiered voice plans to smartphones are numbered.

Me

This just further intensifies the smartphone identity crisis I’ve been going through all year. As a consumer, I feel like I’ll be very happy buying an Android phone or a new iPhone later this year, as both serve my needs so well. Apple still creates a better holistic product due to their vertical control of the whole experience. But at the same time, my long bet is on Android’s success as an open platform. The feature parity is so ridiculous now that I’ll be mostly considering non-OS aspects to make my purchase, like network providers, hardware features and build quality.

Follow-up: This isn’t the DROID I’m looking for.

Last week I posted an article about my thoughts on Verizon’s Motorola DROID after using it for a week. Here’s where I stand after over two weeks now:

I’m not going to keep it. I love its superior functionality. I can overlook the young OS’s shortcomings. The hardware just isn’t resilient enough. There’s no way that it will hold up under my usage patterns for two years.  I have already exchanged one Droid for another unit due to shorts in the loosely-seated headphone jack. The battery cover loves to fall off without user modification. And the keyboard seems to be made of one contiguous sheet of plastic, so I can’t imagine that holding up well over time. For comparison, my original iPhone is still in excellent condition, and no parts have worn out at all.

The OS itself is pretty good overall, but it has some bugs that kill me. Were it on better hardware, I wouldn’t switch devices solely because of them. Most annoying is how I can’t ever stream a long podcast without it dying halfway through – and this happens with any app, it must be an OS problem. Today, the whole screen refused to turn on and I had to remove the battery to force reboot it.

Today, when I came to the point of telling myself, “I couldn’t keep using this for two years, I have to send it back,” it really pained me. Despite the crappy build quality and occasional software problem, I am loving the crap out of Verizon’s network and 3G speed. I love having constant background applications so I have persistent and bug-free connections to Gmail, IM and Twitter. Integration with Google Talk is great, and I’d love to work on actually developing software for this phone. So naturally, I didn’t like the idea of having to return to AT&T and my nice, but albeit feature-limited iPhone.

I may not have to go back to AT&T after all. I’ve been trying to figure out all of the rumors going around about the HTC Bravo / Passion / Dragon. It may prove to be the Google Nexus One, which so far only is known to exist in a GSM variety. But it looks like the Passion is also slated for a Verizon release in January. I think HTC does a much better job at making great hardware, so I would jump at the opportunity to use a 1GHz, keyboard-free Android phone on Verizon.

So I have until January 13 before my “worry-free guarantee” on my contract expires. If the Passion comes out on Verizon, I’ll exchange my Droid for that. If it doesn’t, I’ll be back to AT&T or T-Mobile and my reliable old iPhone until something better comes along on Verizon.