TapExpense 2.5, Mondrianum 2.4.1, and What We Are Doing Lately

It’s a bit embarrassing that we finally got the time to write about a recent TapExpense update, which was released two weeks ago.

TapExpense 2.5 adds an email-based backup/restore mechanism. It is also the last version that supports iPhone OS 2.2 devices. While we no longer receive any inquiry from iPhone OS 2.2 users, we just want to be careful. Some important productivity apps, like Things from Cultured Code, still support iPhone OS 2.2.

We will discontinue iPhone OS 2.2 support from this release on because it’s just about time. With iOS 4 and iPhone 4 now on the market, we should start catching up with many iOS advances. Take the email-based backup/restore mechanism for example. Because on iPhone OS 2.x there is no way to send an attachment to yourself, we are confined to sending you a long, seemingly meaningless string in an email, which is actually a “restore URL” that you can paste into your Mobile Safari’s address bar, which will then open TapExpense to start the restoration process. On iPhone OS 3 and higher OS versions, we will be able to leverage the in-app mailer and make the process smoother.

We have also updated Mondrianum to version 2.4.1, although it’s really just a minor update that changes the version info (“auto update”) URL stored within the app. This is mainly to retire our old file-hosting site in about another two months. We didn’t put 2.4.1 on Mondrianum’s automatic version notification, but we will do that in the next minor release when it’s about time.

It’s going to be a hot summer in Taipei (yesterday the highest reached 38ºC), and we are having a busy time helping our existing clients add iPhone 4, iOS 4 and iPad support into their apps.

We are also making steady progress on our own apps, especially LadyBugz. Some features and fixes have taken us substantially more time than we initially thought, but we believe it will be worth the efforts.

As always, please write us to support{at}lithoglyph{dot}com if you run into any problem, or if you have any comments or suggestions.

Thanks all!