On Tuesday, Phantom Fish released an update to Byline, its Google Reader-slash-offline browser app for iPhone and iPod touch.

Byline's developer, Milo Bird, has been hard at work since Byline 1.0 was released, making improvements to the app based on his users' feedback. Last week, Milo took some time out of his vacation to New York to sit down with us (virtually) and talk about Byline and the app development process.

Does Google make it easy to develop an app that interfaces with Google Reader?

Yes and no. The API for accessing Google Reader is straightforward and well-designed, so from a practical point of view it's quite pleasant to work with. However, it's not formally supported by Google, so there's no official documentation. The API has been around for years now and is in use by a large number of third-party apps, so there are several sources of unofficial documentation, but working out the nuances does involve fumbling around in the dark a bit.

Phantom Fish yesterday updated Byline to version 2.0, adding functionality to browse by tag, and a spiffy new wood-grain interface.

I briefly reviewed Byline 1.0 in July, but wanted to re-visit the application after the update. Byline 2.0 is a Google Reader client and offline browser for the iPhone and iPod touch. After having used beta versions for the last few weeks, I can say with certainty that this update takes Byline head and shoulders above the first version.

Byline 2.0 is faster than both version 1.0 and Google Reader's MobileSafari-optimized interface. Articles are now grouped in folders according to tags you've already set up in Google Reader. You can mark whole folders of items as read, and save items to your phone by starring them. The app doesn't show a splash screen at startup, but instead a "blank" version of the interface, which gives the illusion that the app is hanging for a short period of time. As soon as the list of folders appears, however, loading items was zippy on my iPod touch (connected via WiFi, of course).