A BlackBerry app that doesn't suck

Introducing: Tumblr BlackBerry App

Built by the same brilliant team behind the Tumblr iPhone App, v1 of the official Tumblr BlackBerry App is ready to download!

Click here from your BlackBerry to install

There aren't a lot of good BlackBerry apps out there, but when you see a small company like Tumblr putting out an insanely polished application for what is still the dominate smartphone in the US, you know that they get it. I really hope that the next version of BB OS has a better store. The BlackBerry platform could be so much more powerful if RIM would just streamline the application installation process. And it's not impossible because of Java, because Android has done a very respectable job. Every new BlackBerry shipping with OS 5.0 is capable of reading an QR code. Why isn't there a one-click install feature when you see a QR code?

Also, Tumblr has been on a roll with new features lately. It's pretty amazing the speed at which they are getting stuff out. Respect.

Filed under  //

Comments [0]

Two weeks with a BlackBerry

Two weeks ago I got rid of my iPhone and dropped AT&T for a BlackBerry Bold 9700 on T-Mobile. My impression so far: I love it.

I have all four of my email inboxes being pushed out to my phone. I can look at them in a single inbox or individually. I can (and do) have different signatures for each email account. Since I’m using Google Apps for my email, I actually have the ability to do things like archive and report spam. It syncs both contacts and calendar items flawlessly with Google Sync, in addition to being able to do it natively with the new BlackBerry OS 5.0. Facebook is integrated directly into the address book, so when people call me I see their latest Facebook profile picture.

Google Talk runs in the background and lets me answer IMs the same way one might answer a text message. Google Latitude constantly updates my location and allows me to see where my friends and family are on Google Maps. When I take a picture, I can send it to Facebook or Flickr with a few clicks from within the camera application. I even got into the Foursquare for BlackBerry beta.

My battery time is now measured in days instead of hours. I can use the Bluetooth connection without restrictions to transfer files or use the phone as a tethered modem. Calls are clear, rarely dropped, and I don’t have to worry about signal strength when I’m at home or work, since I just use the UMA and WiFi functionality.

But the most interesting application was something that isn’t new, just something I wasn’t actually aware of — BlackBerry Messenger (or BBM). For those who don’t know, or have never used it, BBM is a collaborative messaging environment that allows you to create groups of up to 30 other BlackBerry users and participate in real-time chats, share pictures, videos, notes, events, and a host of other things. However, most of these features are relatively new to BBM 5.0 and late model BlackBerry devices, which might explain why I wasn’t aware of BBM previously.

All things considered, BlackBerry Messenger is a really neat application with two huge flaws:

  1. It’s too corporate. Your phone is identified by a unique 6-character PIN. No one wants to remember that. The latest version allows you to send people a QR code instead, that will let them add you as a contact or join a group, but it’s far from perfect. Most people still don't know what QR codes are.
  2. It’s proprietary and only works on BlackBerry phones.

Those are my only two gripes. After using it for a little while with a few friends, it reminded me of Google Wave and got me thinking… What is Google Wave going to look like on a mobile phone? Could the future of social networking, email and collaboration lie in mobile, BBM style application? A mobile version of Google Wave could bring BBM style functionality to a host of different devices and break down the barriers that have branded it as a corporate communication tool.

Why a Google Phone doesn't change anything

The Internet was abuzz this weekend with news of a possible Google-branded mobile device. Rumors have it that Google is working with HTC to create a handset they can call their own. Rumors also have it that this handset will be sold unlocked, without the support of a major carrier.

Some people
are responding as if this is a “game changing” announcement. I’m not sure I understand why. Nokia has been selling unlocked, carrier agnostic phones for a few years now – both online and through their stores in New York and Chicago. It hasn't displaced the market in any significant way.

There are only two major GSM/UMTS carriers in the US: AT&T and T-Mobile. Of those, only one of the carriers (T-Mobile) has no-contract plans with data access. AT&T has a no-contract pay-as-you-go plan, but data is limited to 100MB/mo before you start to incur $0.01/KB overage. Thus, an unlocked Google phone is, essentially, a T-Mobile phone.

Moreover, an unlocked phone with no carrier agreement means that you have to pay for the hardware out of pocket, since there are no carrier subsidies like there are with the iPhone. How many people are going to spend $500 and then get locked into a 2-year contract with AT&T? And why would you even want to get service with AT&T? Their data network is crumbling under the weight of the iPhone.

A more disruptive move was when T-Mobile announced they would be offering no-contract plans, in addition to providing 20-month, zero-interest, financing options for handsets (in lieu of contract subsidies). Financing like this means it’s possible for Google to actually move handsets at retail if they partner with T-Moble as a launch partner. If they don’t partner with T-Mobile, they better provide a similar financing option themselves. Few people are going to pay the $400-$600 that a non-subsidized Google Phone is estimated to cost when Apple and AT&T are selling $99 iPhones; and you can get a BlackBerry Bold 9700 from T-Mobile for just $25 out the door (and $25/mo for 20-months after that).

It's unforunate, but a Google Phone doesn't change anything.

Filed under  //

Comments [0]

Moving away from the iPhone

I jumped on the iPhone when it first came out. In fact, I'm one of the only people I know who even has a first generation iPhone. The day after it came out I went to the store to play with it just to see what the hype was about. I wasn't planning on getting one. I didn't even want one; not to mention the fact that I didn't have the money to buy one. After about 30-seconds of playing with Safari I decided that I had to have it. I went to the car, thought about it, then went back into the store and bought one.

Two years later, I've spent over $3,000 on the iPhone and the associated AT&T service plan. Today, I canceled my plan with AT&T, ported my number over to T-Mobile, and purchased a BlackBerry Bold 9700.

Why? Here's why:

  • The iPhone is a terrible phone. Voice quality is terrible. Dropped calls are frequent. Calls often fail to even dial. Voicemails are delayed. Incoming calls constantly go straight to voicemail (which is then delayed).
  • The iPhone is awful if you have more than one email address. The iPhone can only support a single Exchange connection. If you have multiple email addresses or calendars you have to pick the one that you want to be pushed. Everything else must be fetched via IMAP or POP at 15-minute intervals.
  • Push email is unreliable. Many times emails are delayed. *Note: I've only noticed this with Google Sync, and I'm unsure if it's a problem with Google, Apple, or AT&T.*
  • You can only have one email signature. Again, the iPhone just isn't set up to handle multiple email addresses.
  • Battery life is abysmal. It's rare that you can even get through a full day with a single charge. This is why you now see every single socket in the airport occupied by an iPhone user. If you want your phone to be usable for anything that even resembles an extended period of time (by iPhone standards – more than 12 hours) you need to turn off Bluetooth, turn off Wi-Fi, and cut the brightness in half.
  • It costs $100/mo just to have one.
  • It costs $100/mo and you can't even tether it to a computer and use the data plan.
  • As good as it is at text messaging, it's terrible at instant messaging. Since you can't run anything in the background, you really can't use IM at all.
  • The inability to run processes in the background also makes applications like Google Latitude useless.


The reality is that the iPhone is a good pocket tablet. The iPhone is evolution of the Apple/Newton MessagePad, not the evolution of the phone. It's a deplorable phone. I would be more inclined to use an iPhone if it included no phone functionality at all. Maybe if the iPod Touch ever gets a camera, GPS, and persistent data connection I'll go back.

The best thing about the iPhone is the browser. The device would be better positioned as a "must have" if they scrapped the phone functionality entirely and worked out a carrier agreement for data like Amazon has done with the Kindle. Given the size of the application library, that's probably possible. Apple could pay for bandwidth by giving the carrier a portion of revenue generated from the mobile iTunes store. In fact, if an iPhone existed that ONLY featured a browser (even sans the ability to run applications) and some kind of persistent data connection, I'd buy it again. That's why I bought it in the first place.

Goodbye, iPhone.
Hello, BlackBerry.

Filed under  //

Comments [2]

Why open source phones still fail

"Truly open-development, open-source phones like the Nokia N900 will never hit the mainstream in the US because wireless carriers in the country hate the unexpected, writes PCMag's Sascha Segan. The open-source philosophy is all about unexpected, disruptive ideas bubbling upwards, and that drives network planners nuts. So, you get unsatisfactory hybrids like Google Android, which uses some open-source components but locks third-party developers into a crippled Java sandbox. The bottom line is that while Linux the OS, the kernel, and the memory manager are attractive to phone manufacturers, Linux the philosophy — and users banding together ad hoc to create new things — is anathema to wireless carriers."

It’s sad but true.

But even if the carriers were on-board with and open source operating system it still might not work. In fact, it may make things worse. Why? Versioning. Just look at Android. It’s only gone mainstream in the last few months and there are already three different versions of the operating system, all with proprietary UI elements, running on an array of different hardware. There is no uniformity, and application development is pretty lackluster. There are only three versions out in the wild (1.5, 1.6 and 2.0), and it’s already problematic.

RIM has run into problem similar to that of Android, being that there are quite a few versions of the the Blackberry OS, and not every application will run on every version. Some phones can be upgrade, and some can’t. Its up to the carrier to decide what happens, and often they do nothing.

Despite the draconian policies Apple has put in place with respect to application development (and application approval) for the iPhone, it just works. At any given time there is only one version that developers have to worry about: the latest version. It runs on every iPhone, and every iPhone user can upgrade to the latest version of the OS. Applications lack the ability to access certain system functions, and so you never have to worry about them turning your iPhone into a brick.

I have a feeling that even if we had a real open source operating system for mobile, we’d still have problems and the user experience might be even worse than it is today with Android handsets. You might have hundreds of different versions of an OS, with the carrier only supporting one or two. Whether or not an application would run on your phone would be determined by what spin you have and what your hardware specs are. No one wants to sit there hacking away at a command line just to get the GPS to work in some new application you downloaded.

It sucks, but as bad as the Apple/iPhone model is, it’s the best we’ve got.

Filed under  //

Comments [0]