May 24, 2012
This is yet another maintenance release aiming to fix some time zone problems users were having.
- Fixed a bug that could lead to an incorrect cycle date showing on the wheel view
- Changed: No both the Wheel View and the Calendar View go to Today when resuming from background
The first hopefully is the last bug fix related to the time zones. Internally all dates are now absolute. That means they won’t change if you travel to somewhere that has a different time zone than where you are usual at.
The second item was much requested because it would save the user from having to tap the Today button upon returning to the app from background.
Update June 1st: the update was approved and is now on the app store.
Mar 28, 2012
I thought I was smart when refactoring some code in DTAboutViewController to use block-based animations. Turns out that I had not considered backwards compatibility for 3.x when doing that simple change. This caused some unlucky users (still on iOS 3.1.3) to get the update pushed via iTunes, but then finding themselves unable to launch the app.
I do plan to cease supporting 3.x sooner or later, but not like this. The proper way is to raise the deployment target when implementing features that require 4.x. This way people unwilling (or unable) to update their devices just won’t be receiving those new updates but will still be able to continue using the old version.
- Fixed: Incompatibility with 3.x causes app to crash
- Added: Alert when user tries to send support e-mail but has no account configured
- Fixed: Tapping on today button in cycle view would show the wrong day in cycle view.
- Fixed: Tapping on the calendar button in Wheel View would lead to the wrong day in calendar view (in some time zones)
The update has been submitted to Apple and should be available soon.
Update April 4th: … the update is now available on the App Store.
Feb 03, 2012
This is a maintenance update. There was a bug in DTAboutViewController which caused a crash under iOS 5.
- Fixed: Crash on iOS 5 when opening About Section
The update has been submitted to Apple for approval.
Update Feb 8th: Ready for Sale. It should be available shortly.
Aug 31, 2011
There was a stupid problem before this version that could only be seen by users who where traveling between time zones. Notes that you made for a specific date would disappear when you moved into a different time zone and reappear if you moved back. This taught me that it is a bad idea to use an NSDate for a primary key.
Updating a lower version iWoman will restore all entries that might have disappeared. In very rare circumstances – involving traveling more than 12 time zones – some entries might end up the day before or after the day they were originally entered on.
The second change came from a user request who wanted to see the day number on all days of the cycle view. Previously it would not be shown on fertile days.
May 18, 2011
René Lindhorst attended the MobileTech Conference in Munich in April. He snapped this picture of a slide stating “we use our phones to manage every aspect of our lifes”. You can tell that this conference was in Germany due to the misspelling of “lives”.
I still love that they chose our new 2.0 iWoman icon top left, as indeed my wife (and many other humans of the female persuasion) use iWoman to manage a very important part of their lives. And thanks for putting it in good company: I see Pages, Evernote, Carcassonne and Angry Birds there, all apps that I also have installed, too.
Mar 09, 2011
In this quick-fix update for iWoman I addressed a bug that could only be seen by users of the basal temperature feature.
- FIXED: The basal temperature chart would only show the first 30 entered values.
Update was approved by Apple on March 8th it is available via the app store.
Jan 16, 2011
The previous version of iWoman has a severe problem if you have an existing database that needs to get migrated. Turns out that old iPhone might take too long doing that. And if it takes longer than a couple of seconds for an app to start then there is a watchdog timer in iOS that will outright kill the app.
Also there was a graphics glitch on the list view which has been remedied. I am really sorry for all these glitches. I promise you that they have not been intentional and I am quite embarrassed by them.
The Update has been submitted to Apple and should become available soon.
- Fixed: Graphics glitch on list view on 3.x devices
- Fixed: DB Migration is now done after app startup – instead of during startup – to prevent app termination by iOS.
Hopefully with this patch migration and usage should be smooth on 3.x and 4.x alike. If so then I can concentrate on additional features. The app is doing pretty well in Russia and so I will add localization as a “Thank you!” for the Russian ladies. Also I am thinking about adding Japanese to see how this might affect sales there.
Dec 20, 2010
It’s been a long long time since I last updated iWoman, more than a year to be precise. I have to admit the success of iWoman made me lazy. Why would you want to change something that is selling so well? In fact iWoman topped the Healthcare charts in several countries for a long time. Other projects seemed be be more important.
I have to credit my wife who kept bugging me about how I obviously did not care about we women on Earth. She is using iWoman for about years now and I kept updating her iPhone with the latest builds. For a long time iWoman was stuck right between versions, but suddenly – about a month ago – motivation returned. I wanted to polish iWoman into the jewel that is was so long ago and add all these features that customers kept requesting.
iWoman 2.0 is now (finally!) available on the app store.