RunningTotal Update Notes
RunningTotal 1.0 was released on 3 May 2009, and is compatible with any iPhone or iPod touch running iPhone OS 2.1 (a.k.a. iOS 2.x) or greater. When RunningTotal 1.0 was released, iOS 3 was in early beta, and testing against it was inconclusive (we didn't uncover any problems, and even if we had run into a problem, and we didn't, what was up with that anyhow.) To say that RunningTotal 1.0 was conservatively designed, is to put it mildly. We held up release of the app almost to the point of demanding that it would survive (secondary consequences of) an EMP attack. That's the way we think.
Fast-forward to the era of iOS 3, and RunningTotal 1.0 still continued to work great. Tested against iOS 4, it still continues to work great. Any minimal (i.e. we didn't change anything) update submitted to Apple would verify that. We use the original (v1.0) app in the context of iOS 4 on a daily basis.
RunningTotal 1.1 is in process and will require iOS 3.0 or greater to run. As of now (July 2010) Apple will no longer allow us to submit app updates that support iOS 2.x. We can't do anything about that.
A bit of history: The original "Release" version of RunningTotal (i.e. 1.0) was version 2.4 internally to us. We never released versions of RunningTotal prior to that because we wanted to come out with an app that was as solid as it gets, and we think that we achieved that. You would not believe the amount of testing that went into this app. There is intense pressure on developers to release version after version of an app, fixing problems that are minutiae that could have been fixed with a bit more time to "really get it right." This is not the way we do things. Please look at our update schedule in that light.
Getting more participatory here: we have some decisions to make. We have had repeated requests to incorporate a "scheduler" into RunningTotal. This would be a software mechanism that the user could employ to have a certain action taken upon a table on a monthly basis, automatically (i.e. without adult supervision.) Is this something that you might be interested in? In nominally crazed fashion, we're never closed to outside opinions. Huzzah.
There is a very strong likelihood that RunningTotal 2.0 will be released as compatible with iOS 4 only, because there are a bunch of technologies in iOS 4 that we would like to use, and by the time it rolls around that we can do a release against those technologies, y'all will be yawning to have already upgraded to OS 4.
For those users of RunningTotal (or any other app) who have issues with the iOS 4 upgrade, we would like to hear from you, as it pertains to the subjective speed of the current version (1.0 or 1.1) of RunningTotal.