Buy it now...

Known Issues

As much as I want to believe it, Countdown Calendar isn't perfect. Here's a list of past and present issues with the app.

Current version in the App Store.

No known issues.

Fixes the following issues:

Fixed problem where countdowns that terminate during Daylight Savings Time are displayed as "one less" than they should be.
Fixed problem where countdowns more than approximately 20 years in the future or past would display an incorrect value.

Fixes the following issues:

Fixed bug where certain timezones would display incorrect countdown figures. (Canada Mountain Standard Time, in particular.)
Countdowns that expire today are shown in a "today" category, rather than "in the future."
Units don't round. This means that you can enter your birthday and it won't say you're 40 if you're really 39.6.
Sending countdowns is integrated into the app...no having to jump out to Mail.
New icon.

Fixes the following issues:

Monthly and yearly countdowns could incorrectly display as "in the past"; bug has been fixed.
"Today" countdowns are now displayed at the top of the list, rather than the top of the "in the past" list.
Enlarged "hit area" on detail arrows so they're easier to push.

Submitted to App Store...approval hoped for by mid-July.

Minor bug fix release:

Fixed a memory management problem related to the Countdown Repository.
When viewing countdown notes, the title of the Note window displays the Countdown Name rather than "Countdown Notes:".

Fixes the problem on pre-release versions of iPhone OS, where countdowns couldn't be edited.

The improvements...

Notes can be added to Countdowns, to describe what they're for, or to keep track of a project the Countdown is representing.
Day of week displayed when setting the Countdown date.
Human-readable date is included in e-mail when Countdowns are sent. (Lets people who don't have Countdown Calendar know what you're talking about.)
Bug fixed: now when creating a new countdown, the name is capitalized by default.

The following bugs were fixed in version 1.0.2.

Fixed a bug that kept countdowns that happened in the past from displaying in the online Countdown Repository.
Countdowns in weeks, months, or years now show a decimal component (i.e., 5.5 weeks, when before that was displayed as 6 weeks.) But only if the number in question is less than 10.
Fixed a bug that was saving countdowns every time the application was closed. Now saves only if countdowns were modified, added, or deleted.
Fixed a memory leak related to downloaded countdowns.
Countdowns are saved in the case of a memory warning as a precautionary measure.
Fixed a bug where if a countdown is downloaded from the Countdown Repository multiple times then deleted, the app would crash.
Believe I fixed a bug where the app could crash while browsing through the Countdown Repository.
"Submit Countdown to Repository" button should always work.
Countdowns older than 65 years should display the proper count number.

There is no version 1.0.1.

App sometimes crashes while browsing Countdown Repository. Fixed in Version 1.0.2 (see below.)
Copying the same Repository countdown into a list more than once, then trying to delete one of those Countdowns, causes the app to crash. An obscure bug, but a bug nonetheless. Fixed in 1.0.2.
Repository countdowns that happen in the past aren't displayed. There are a bunch of cool Countdowns in there that no one can see! Fixed in 1.0.2.
"Submit Countdown to Repository" button sometimes does not work. This is due to a bug in iPhone OS 2.2. Fixed in 1.0.2.
Countdowns for a date more than 65 years in the past show up negative. Fixed in 1.0.2.

Don't see your bug listed here? Contact for technical support, suggestions, anything.