Mobile Site Generator Update: v1.1 (RSS feed parsing)

Last night I pushed out the first major update to the Mobile Site Generator. There’s one big new feature: It can now pull in content to a page from an RSS feed! This feature assumes your web server is running php with cURL enabled. If you don’t know whether your server meets these requirements, there’s one easy way to find out: Try it out 🙂

I consider this feature to be pretty experimental, so I’d love any feedback on how well it works and whether I’ve explained what it does well.

Note that this isn’t a feature you have to use. If you want, you can keep using the generator and pretend it doesn’t exist. I also recommend not using it more than once in your generated mobile site – pulling in multiple RSS feeds can slow down the page dramatically. I hope to build in some ways around this problem in the future.

I’ve been thrilled to see the response to the generator! I’m glad that people are finding it useful. If you’ve launched a site and used the generator at some point along the way, please let me know about it. I’d love to build a practical showcase of what this thing can do.

Educause ELI Online Spring Focus Session

Today I presented briefly on mobile site-related things as part of Educause’s Online Spring Focus Session on mobile learning. Someone asked for my slides, so here they are! My previous slides from Handheld Librarian expand on a lot of what’s here.

Today’s slides, on slideshare:

(A couple of images got scrambled in the process of uploading to SlideShare, but all the content is intact)

Handheld Librarian & Mobile stats

I’ll be speaking later today as part of the Handheld Librarian II online conference. My Powerpoint slides are already online here, but I wanted to note some things I’ll be talking about that didn’t make it into the slides:

First, while there’s many other available frameworks than just the two I talk about, I do want to specifically point out the MIT Mobile Web project. The folks over at NCSU have done a great job implementing it with their library’s mobile site. They’re talking about it in a session right after mine, so I won’t be covering it in too much detail. MIT’s code is fairly robust, but also much more complex to get set up and running than iUI or Jason Clark’s work.

Second, some interesting stats. From two separate reports, both with data about December 2009. Looking at them side by side:

-Apple has 25.9% of the US smartphone market share (in devices sold), but iPhones also make up 54% of US mobile web traffic.

-Android has just 5.2% of the US smartphone market share (in devices sold), but makes up 27% of US mobile web traffic.

-Blackberries have an astonishing 41.6% of the US smartphone market share (in devices sold), but make up just 10% of US mobile web traffic.

There’s an important lesson here to keep in mind when choosing which devices to support with a mobile website. At first glance, looking at Blackberries’ market share alone, they seem to be the platform to support – it’ll get the most users in, right? Not when they use just 10% of all mobile web traffic! The heaviest users, the people we should be targeting now with our services, are on Android and iPhone. By supporting their combined 31.1% market share of devices with our our mobile sites, we’re available for 81% of mobile web traffic. That’s a pretty solid return on investment. I’m not surprised by these results, but it’s always nice to have numbers to back up intuition.

This isn’t to say that blackberries should be ignored – they’re just not the best target audience for a pilot program.

Mobile Site Generator

I’m really excited to launch a side project this morning that I’ve been working on for a while:

Mobile Site Generator

After filling out a form with page titles and few other bits of info, the generator spits out a fully functional mobile site (tested on iPhones, iTouches, and Android devices) ready for uploading to your server as an HTML file!

I’ve been asked a lot of questions about how we made the UNC Libraries’ mobile website. When I start to talk about the iUI framework we used, I see a lot of eyes glaze over. But it’s really easy! I’m not an expert coder, honest, and I made it work. Anyone who has basic familiarity with web development and a little time on their hands to puzzle out a few details can use iUI.

But while I’ve seen a lot of talk about mobile sites for libraries, I don’t see nearly as many actually implementing them. I think a lot of librarians are intimidated. But IUI’s code is actually so simple that I was able to automate its creation! The Mobile Site Generator will hopefully help people over the first hurdle: it creates a framework for a mobile site that you can then tweak & customize to you heart’s content.

As you’ll no doubt see immediately after clicking the link above, the MSG (gee, what a great acronym I picked!) has an interface that’s… shall we say less than ideal 🙂 I plan on making it prettier with time, but I wanted to get it functional and online in time to point it out in some presentations I’m giving in the near future.

There’s more information on what the generator does over on the MSG page. I welcome your comments and suggestions! You can leave comments here, on the MSG page itself, or just e-mail me.

eBooks – Who’s doing it right?

I’ve spent a lot of time lately thinking (and writing) about eBooks, usually taking a pretty negative slant toward existing eBook publishers and vendors. DRM, distribution models, even publication timelines – much of it is a huge mess.

But I don’t want to seem too negative – I still think eBooks as a concept hold massive promise. It’s just many of the current implementations that’re flawed. So who’s doing it right? Here’s a handful of companies and products which I think are on the right track:

1. SpringerLink
Much of my thinking centers on the consumer publishing eBook panopoly – the Kindles, Nooks, and similar devices of the world. But there’s of course an academic side to things too. I have major beefs with a lot of the vendors and publishers who provide eBook packages to universities & colleges. Most of these are a topic for another post. But one thing I want to cover here: Many of them commit one of my pet peeve sins by making the books non-downloadable. They can’t be used on any kind of personal eReader device, or even viewed on a PC without an internet connection. But the SpringerLink collection that we subscribe to at UNC provides simple, clean, downloadable PDFs. There’s no password protection on the files, no DRM, no clunky web client we’re forced to use. They trust users to download a chapter and use it responsibly. As a result they’re the first eBook collection I search and show to students.

Sure, I wish SpringerLink had a more flexible format than PDF, but this is a step in the right direction. While other vendors like eBrary are rushing to finish off what will no doubt be limiting device-specific apps for their content, Springer lets readers choose how to consume their text.

2. Fictionwise
Fictionwise.com isn’t perfect, but they’re still my favorite eBook retailer. They sell a large portion of their titles DRM-free, which means they can be read on virtually any device or computer in perpetuity. There’s no license keys to maintain, no chance of a distributor retroactively taking back a sale. They also provide an archive of my purchases – I first bought a title from them in 2003, and I can re-download that book as much as I want today. I can even still get to the titles I purchased which they no longer sell. I wish their catalog of non-DRMed books would grow, especially among current bestsellers, but Fictionwise is still the only place I buy my eBooks from today.

(One caveat – Barnes & Noble bought Fictionwise last year. I hope B&N lets FW keep its independence.)

3. Calibre
eBook file formats are far from standardized. There’s .epub, .lrf, .html, .mobi, .pdf… the alphabet soup goes on forever. And of course no one device or program supports them all. The situation is a head-scratcher, and that confusion costs consumers & students time and money. Once upon a time it was a nightmare trying to convert from one format to another. Then along came Calibre.

Think of it like itunes for eBooks. It converts from almost any format to any other format, provides sophisticated yet user-friendly metadata management, and even syncs files with eReader devices. As a bonus, it’s open source & free to download!
Calibre single-handedly increased my ability to read eBooks by roughly 100% (my very scientific measurement, yes), and decreased my frustration even more. It doesn’t work with files locked down via DRM, but that’s a fault of vendors and not Calibre.

4. Comics by Comixology
Technically this is about comics, not simple text, but either way it’s still eBooks of a different sort. Comics by Comixology (henceforth referred to as simply ‘Comixology’) is an iPhone app which sells downloadable comic books. Many of them are adapted from print versions, but optimized very well for the iPhone & iPod Touch’s smaller screen. Panels zoom in and out and flow together. And in a first for digital comics, Comixology even sells issues from many major print publishers like Marvel and Image.

The comics only function on the iDevices, of course, which is something that would usually bug me. But the user experience is so good that I’m willing to overlook it for now. And then comes what I like best about Comixology – the price. Most issues are either $.99 or $1.99, which frankly is what a comic book should cost in any form. Many print comics now cost $3.99, and then after that ripoff I have to find somewhere to store them. As a result, my comic buying in the last couple years has dropped way off.

So $.99 for something I don’t have to find storage space for is a very attractive alternative to me. Example: I recently wanted to read the newest Atomic Robo collection. Amazon charges $12.89 for the print version, down from an $18.95 list price. I picked up the whole thing on Comixology for $4.95, and had a great digital reading experience without taking up space on my living room shelves. Cost effectiveness trumps a lot for me. Many times publishers charge resellers like Amazon the same wholesale price for both print copies and eBooks. This baffles me to no end. Comixology and their content providers recognize how much cheaper digital distribution is, and adjusted their prices accordingly.

I consume comics differently than I consume books. Comics by Comixology (despite their awkward name) is smart enough to realize that I’m not alone in this, and found a way to make the restrictions I usually foam at the mouth over become a palatable choice.

(note: Comixology has multiple apps for the iPhone, and I’m talking about the one specifically called ‘Comics by Comixology’ here.)

Step into the social circle

I was googling around for something work-related this afternoon, and noticed some results it was finding on Flickr. After a quick double take, I realized it was finding a few photos from my Flickr contacts. Weird coincidence, right? That was my first thought. Then I looked closer, and noticed that Google is running a new beta feature called ‘social circle’: http://www.google.com/s2/search/social

(OK, maybe it’s not so new – the Google Blog mentioned the feature’s launch last October. But it’s new to me!)

Essentially, Google knows who my friends are and now searches each friend’s personal web of content. The idea, I guess, is that results from my friends will be more relevant.

But then I thought to myself “Hey self, Google doesn’t own Flickr, Yahoo does! How do they know who my Flickr contacts are?”

After poking around, as best I can figure out their data mining goes something like this:

1. I have a google profile page (http://www.google.com/profiles/Chad.Haefele)

2. On that page, I have a link to my twitter account.

3. Google pulls in my twitter contact list, presumably via the Twitter API.

4. Google checks to see if any if anybody else with a google profile page listed a twitter account that matches someone I follow on twitter.

5. If it finds a match, Google takes a closer look at the matched person’s Google Profile page. Other sources from that person’s profile are added to my social circle search results. If they happened to list a Flickr account, photos from it show up in my search results whether or not I’m actually connected with them on Flickr.

At first I found this vaguely creepy, complete with brief paranoid visions of Google’s slimy tentacles reaching out across the web. But the more I think about it, the more I like it. Every bit of this data comes from a source that the creator specifically allowed to be public. It might be an order of thought removed from what most people consider when posting a link, but I think it’s still kosher. A conscious decision to make this info public was necessary. And I love seeing what simple things like APIs and RSS feeds can mash together.

Most importantly being able to search my social stuff like that in one place is extremely handy. More and more I find myself searching my own twitter contacts’ streams or my flickr contacts’ photos for things I need and opinions I trust or that one link I know I saw somewhere weeks ago and now want to go back to. By adding these search results to my standard daily googling, I get the same high utility from those results even if I wouldn’t have thought to search my social stream directly.

Every so often it hits me all over again: We live in a pretty amazing world. In a lot of ways, the internet still seems like magic to me.

Mobile apps vs. Mobile web

Apple loves to tout their 100,000+ iPhone apps. Android recently topped a respectable 20,000. These are both impressive numbers, but how often do we really need an app instead of the good old-fashioned web?

Apps lock up data and go against one of the central ideas and advantages of the open web – the ability to link between pages.

A user recently asked if our mobile app could add links to Worldcat items from our own mobile catalog items. I didn’t know the answer, but thought it sounded like a worthwhile addition if possible. I remembered seeing a Worldcat mobile interface a while back, and went looking for it once again. I found that Worldcat recently moved from a mobile website version to a mobile app version.

A mobile website is pretty self-explanitory. It’s a website formatted for a mobile screen that you load in a browser. It’s part of the web as a whole. A mobile app is more like any application on a computer – you launch it, do what you need to, then close it down. But mobile apps as they exist today are largely walled gardens, and don’t share data with each other easily (if at all). So while Worldcat has all their records very nicely displayed in this app, it’s impossible for our local catalog to link to them from the browser*.

Worldcat’s regular (non-mobile) site is very linkable. If I want to link you to The Mysterious Benedict Society’s record, I just have to give you this to click on. That’ll still work in a mobile browser of course, but the resulting page is clunky to view on a smaller screen. When OCLC has obviously gone to a lot of effort to get their data into a mobile format, it just seems a shame to ultimately lock it away from other developers inside an app.

And believe me, a native app for a phone takes a lot of effort. I originally tried to write one for the UNC catalog, but the fact that I’m not much of an Objective C programmer reared its ugly head and I had to abandon the effort. The return on the massive investment of my time and effort it would have taken to code an app just didn’t make sense. And a library catalog app wouldn’t even have any extra functionality over the mobile website catalog I ended up with. Our mobile site works on almost any modern smartphone, but if I’d somehow managed to bang out an iPhone app that app would work exclusively on iPhones. I’d have to start from scratch again to get the catalog working on an Android or Palm phone, and what about the countless phones that don’t run apps at all? They’d be left out in the cold.

On the flip side, Apps certainly do have their time and place. They have greater access to the phone’s hardware than a browser, and can use things like the phone’s camera in ways that a mobile website currently can’t. But unless a hardware ability is central to an app’s purpose for being, I’d be hard-pressed to justify developing a full app instead of a mobile website. And now that many mobile browsers can access the phone’s GPS information, a webapp can actually do some basics of what were formerly hardware tasks. For example: I’ve become minorly hooked on the location-based service Gowalla lately, and Gowalla has no Android app – just a mobile website that can use the phone’s GPS to find where I am. It works really well. Full apps are also useful for offline tasks, since they allow caching of data & tools locally for use when there’s no connection to the web.

And apps do have an undeniable coolness factor. It’s a lot more impressive to say “Download our app in iTunes” than to give someone a URL to a mobile site.

But our library catalog & website don’t need a camera, and the very nature of a catalog is searching for information online – nothing can be stored locally in a way that makes any sense. Having a deliverable end product also wins out over the coolness factor with me, especially since I never could have completed the ‘cooler’ project in the first place 🙂

For the current state of the mobile web, I don’t think a mobile app’s advantages are enough for libraries. It’s important to get our information into as many of our users’ mobile devices as we can, and as quickly as possible. An app might come later; if the publishing world ever permits libraries to loan eBooks in a usable fashion, then sure a library eReader app would make sense to develop. But for now, when most of our mobile work is repackaging web data we already have into a new format, a mobile website is the way to go. It’s quicker to develop, works on more devices, preserves linkability, exposes our mobile pages for other developers to build on, and maintains the core functionality we’ve spent so much time developing for our non-mobile websites along the way.

(*As a side note, I did eventually dig up Worldcat’s old mobile web catalog. It still exists! But it doesn’t support direct linking either. This is another thing I’ve run into repeatedly – another argument/rant/post for another time.)

Review: Motorola Droid

Now that the Droid has been out for over a month this review might be a little questionably useful for early adopters, but I’m going to go ahead and write it anyway 🙂

In short, I like the Droid a lot. It’s the first smartphone I’ve ever owned (after 2 years of living on an iPod Touch mostly happily), and lives up my expectations.

Fake Q&A with myself:

How is the Droid as a plain old phone?
Call quality is excellent, better than any other phone I’ve ever owned. It also gets a stronger signal than my previous phone (an env2) did in a lot of places. Granted I don’t make a lot of phone calls, but in over a month of use I don’t think I’ve dropped a call once.

How’s the battery life?
In a word: OK. In a day of average use I drain the battery to about 15%. For me, ‘average use’ means maybe 10-15 minutes of actual phone calls, and the rest of my use is on the data side. Browsing the web, using apps, maybe a bit of GPS navigation, etc. But for a real power user who wants to rely on more battery-intensive tasks like GPS for all day use, the Droid’s battery simply won’t cut it. Invest in a car charger and a docking cradle for your desk. I have both of those, and have managed to get myself into a routine of charging the Droid whenever I’m not using it.
Incidentally, I love that the Droid uses a standard mini USB plug for charging. This is the first time in my life that I haven’t had to buy all new chargers when upgrading a phone.

How’s the screen?
It’s a thing of beauty. I never thought my iPod Touch screen was anything to sneeze at, but it looks downright blurry next to the Droid. I can read much smaller font sizes on the Droid than I ever could on the iTouch.

How’re the apps?
I’ve found an app for almost everything I want to do on the phone. See this post for some of my favorites. My favorite thing about the Android app store is that I can get a refund on any app for 24 hours after purchase. So trying out new things is very easy & risk free.

How’s the physical keyboard?
The buttons are closer together than is ideal, but I got used to it quickly. I have tiny fingers, so others might not like it as much as I do. I should also note that I’m the only Droid user I’ve heard of who uses the physical keyboard whenever possible – everyone else I know prefers the on screen one. The on screen keyboard is fine, I just find I can type faster on the physical option.

How’s the browser?
Mostly good. It does some strange things with auto-formatting text for a mobile screen. This is usually helpful, but sometimes screws things up a bit. Much fuss has been made over the Droid browser’s lack of multitouch. I don’t really miss it as much as I thought I might – double tapping to zoom in works just fine.

Alright buddy, this is a glowing review so far. What don’t you like about the Droid?
There are definite shortcomings. The camera is one of them. It’s supposedly a 5 megapixel camera, but I would never guess that from the results. Any photo not taken in very bright lighting is grainy. The autofocus works well, but the interface for changing focus options is terrible and difficult to get to quickly. The camera has a LED flash, but it’s pretty useless for taking pictures. I get far more use of the LED as a flashlight than an actual camera flash.

Media syncing is entirely user-unfriendly. I’ve been spoiled by using iTunes to get music onto the iPod Touch, and miss it dearly. I’ve found some third party solutions to sync music & video onto the Droid, but none work well enough that I want to endorse them here. Google needs some native software for this, and pronto.

Media playback is kind of mediocre. Again, spoiled by iPods. It works, but the interface isn’t nearly as well thought out as Apple’s.

There’s no bluetooth voice dialing. A small thing, yes, but also something that has no excuse for being left out. My last three phones all had it, and not having this feature makes it technically illegal to make a call while I’m driving in North Carolina – even with a headset.

Let’s counteract that with some good: What are your favorite things about the Droid?
Running apps in the background is amazingly useful – far more than I expected it to be. Swapping between different apps on the Droid is far faster and more convenient than on iDevices.

The GPS driving navigation feels like it fell out of a time machine from 10 years in the future. Melissa and I were in DC recently to see a Swell Season concert. I spoke into my phone: “Navigate to the Swell Season concert in Washington, DC”, and it knew where I wanted to go! Behind the scenes it used the web to figure out the venue of the concert and direct us straight to the front door. It also pulls in live traffic speed info, which more than once has let me plot a detour around upcoming traffic jams.

Full integration with Google Voice is extremely promising, and I’m inches away from converting over to a GV phone number for daily use.

I really love that apps can play nicely with the browser. For example, I installed a great app called GeoBeagle to use for Geocaching. When I click on a link to a cache on Geocaching.com, an option pops up – would I like to load this link in the browser, or save the cache it points at into GeoBeagle? Similarly, clicking on a podcast feed asks me if I’d like to subscribe to that podcast in Google Listen.

Widgets on the home screen are extremely handy & useful. I can control music playback, check the weather, change screen brightness, toggle wi-fi, turn on the LED as a flashlight and more without launching any apps or going into any settings menus.

Summary?
The Droid is a great smartphone. I’m very happy with it and it fits into my daily information needs very well.

Publishers don’t understand e-books

This Wall Street Journal article touched many nerves for me: Publishers hold back e-books.

So hold on, I’m going to get a bit ranty and this’ll probably be a long post 🙂

Summary: Two major publishers have decided that they’re going to hold back e-book versions of their titles for months after the hardback release.

From the article, here’s their justification:

“The right place for the e-book is after the hardcover but before the paperback,” said Carolyn Reidy, CEO of Simon & Schuster, which is owned by CBS Corp. “We believe some people will be disappointed. But with new [electronic] readers coming and sales booming, we need to do this now, before the installed base of e-book reading devices gets to a size where doing it would be impossible.”

A much better (and more profitable) course of action would be to simply embrace the e-book world and figure out how to adapt to this new ecosystem. Change is coming, and burying their heads in the sand isn’t how publishers will survive.

Some publishers try to make the argument that people have had the choice to buy a hardback immediately or wait for the cheap paperback for decades. And surely placing an e-book release between those two options just extends this model, right? They have this nonsensical vision that people with e-book readers will run out and buy hardbacks instead when their e-books are taken away. This could not be more wrong. Here’s what’s going to happen instead:

Meet Consumer Bob. Consumer Bob invested a lot of money in a Kindle. He obviously bought the device because he wants to read books on it, right? So Bob hears about a new book on TV and thinks he’d like to read it. Bob can’t find that book for his Kindle. At this point, Bob will do one of two things:

A)If Bob’s tech-savvy he’ll pirate the e-book he wants. Publisher gets no money.
B)If Bob isn’t tech-savvy he’ll buy another e-book to read, and probably forget the first book ever existed. Possibly a different publisher gets money.

Bob spent $250+ on his Kindle, and you better believe he wants to get use out of it. After plunking down that chunk of change, buying a paper book can feel a bit like wasting money. As a Sony Reader owner, I feel this sometimes myself. But Bob is also used to instant gratification and instant delivery of e-books, and doesn’t want to wait for the print version to arrive by mail or a trip to the store. Bob likely isn’t going to change his habits.

But let’s go back and look at part of that article quote again:

“…we need to do this now, before the installed base of e-book reading devices gets to a size where doing it would be impossible.”

What? Consumers are finding something new they want, and your response is to deny it to them? How does that make any kind of business sense? With that attitude you deserve to hemorrhage money.

Another article quote:

“Even as the retail price of many new hardcover novels creeps above $27, Amazon and Barnes & Noble boast many new best sellers for only $9.99 in the e-book format.

Increasingly, publishers have come to fear that the bargain prices will lead consumers to conclude that books are worth only $10, or less, upsetting the pricing model that has survived for decades.”

You know what? They’re right. A DRM-locked e-book simply isn’t worth $27. It’s barely even worth $10. I’m not going to pay the same amount for an e-book that a paper copy would cost me, when I can actually do LESS with that e-copy than the print: I can’t loan it, resell it, or donate it. So I will never ever pay full price, or near full price, for a DRM-locked e-book. Ever. And anybody who does hasn’t thought things through. I’d only consider buying DRM books with a massive (something like 75% or more) discount over the print version, unless the e-version has some other equally massive advantage.

But publishers even shoot themselves in the foot when they stumble on an e-gold mine. Stephen King’s new book, Under The Dome, is over 1000 pages. I don’t want to lug that back-breaking monster around with me, especially on the bus. I want to have it on my phone or e-book reader. This is a case where an e-book has clear convenience advantages over a print version, maybe even enough to overlook DRM issues. I was planning on buying it.

But King’s publisher, Scribner, has decided to shoot the e-book in the head. And not once, but twice. First the e-version won’t be available until 12/24, a full six weeks after the print version was released. Second, they’re charging wholesale prices for the e-book to distributors (like Amazon and B&N) of $35.

My moral outrage from their pricing issues aside (there’s no way they’ll ever convince me that it costs the same to print and ship an e-book as a print book), I REALLY don’t want the massive print version. No matter how discounted it is. So I’m left with just one option to acquire the book legally: Buy Under The Dome as an e-book on 12/24. This is the exact same end result as if the book was released the same day as the print version, 11/10. All Scribner has done is provided me with 6 weeks to forget that I want the book. 6 weeks to find something else to read, or maybe run across negative reviews and decide I don’t want the book after all. A thousand things could make me change my mind about buying the book. Forcing me to wait gains them nothing, and only introduces unnecessary risks into the question of whether or not they’ll get money from me.

And meanwhile I hate to break it to them, but despite Scribner’s best efforts Under The Dome is available as an eBook right now. It’s been pirated, of course. A quick search of the web shows a pirated version, likely scanned in by a large cooperative group, freely available all over the web (and with no DRM!). So Scribner has created an ecosystem where piracy is literally the only option for potential customers who would otherwise line up to give them money, AND that piracy delivers what’s actually a superior product with no DRM. King is a high profile writer with die-hard fans who want his book immediately, not six weeks from now. What are they going to do?

The sad thing is that Scribner will likely use this piracy situation as supposed evidence of how the e-book system doesn’t work and is killing the publishing industry. And they’ll never even see through their own fear, uncertainty, and doubt to realize that the root causes live in their own backyard.

Indispensable Android Apps

About a month ago I finally joined the smartphone world. Verizon released the Motorola Droid phone, which runs on Google’s Android software platform. I’m 95% satisfied with the phone, with only a few minor quibbles. I’ll get into those in another post. But first, here’s some of the 3rd party Android apps I’ve used most often:

Aldiko: An e-book reader, every bit as good as Stanza is on the iPhone. And that’s high praise.

Android Scripting Environment: This one’s just a bit of nerdy programming fun, you can write quick python scripts to do things on the phone – speak words, read your text messages, scan & process barcodes, etc.

Astro: A great file browser & manager, a category which Android oddly doesn’t have a default app for.

CardioTrainer: Keeps track of your workouts via GPS. I use it on my bike with great results. Kind of like Nike+, but free!

DockRunner: Kicks the Droid into its alarm clock nightstand type mode, which usually can only be accessed by placing the phone in its official Motorola docking cradle (and that cradle costs $30).

Listen: Google’s podcast downloader & organizer.

Mototorch LED: Turns on the Droid’s camera flash LED for use as a (surprisingly powerful) flashlight. Plus as a bonus, you can use the LED as a strobe or to send morse code flashes – always handy.

Pixelpipe Lite: For some reason the Droid’s built in photo uploaders strip all EXIF data out of the photo while uploading – including date stamp and rotation info. Pixelpipe is the only Flickr & Twitter photo uploading app I’ve found that preserves this data.

Twidroid: This app’s latest update took it from a good Twitter client to a great one.

That’s it for now! Look for a more in-depth Droid review at some time in the semi-near future.