Changes

- FIXED a bug that could lead to new cycles not being added to the cycle list upon pushing the Add button.
- ADDED functionality for importing and exporting your database to a text file which is accessible via iTunes.

The update has been submitted to Apple and will be released as soon as it is approved.

Changes

• 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.

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.

Changes

• 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.

Change

• 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.

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.

Changes

• FIXED: Items would vanish from calendar view if user moved between time zones.
• MODIFIED: Now the day number is shown for all days in cycle view.

The update has been submitted to Apple and we hope for a swift approval.

UPDATE Sept 7th: the update is now available on the app store.

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.

Changes

• 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.

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.

Changes

• 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.

Update Dec 31st, 2010: Update has been submitted to Apple. We hope for a swift approval.

Update Jan 5th: I was made aware that I had the deployment target on 4.2 effectively making the update unavailable for half of my user base. Because of this I pulled the 2.0.1 and submitted it again with a correction for this. This will delay the availability of this update once again.

Update Jan 6th: Update has been approved and will be downloadable shortly via the app store. Also because of the fierce competition we saw ourselves forced to drop the price permanently to $1.

The problem with the incorrect menstruation values came from an internal change to allow for importing another vendor’s file format. I had represented the values with 0,1,2 while the new representation was 0 for none, 1, 2, 3. This caused a medium value to become a low. A heavy became a medium and a low became an invalid value which got incorrectly corrected to medium as well. The fix will check for the backup file of the import and correct the values.

Then there was an annoyance which you would only see if the app was kept running in background over a date boundary. It would immediately exit i.e. crash. That’s fixed as well.

I’m terribly sorry for any inconvenience these bugs might have caused and I hope that you will love to use iWoman even more now that you see how committed I am now to make it a pleasant experience.

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.

Under the hood the database has been moved from basic SQLite to CoreData and all the graphics have been polished to perfection. Of course fully Retina. But that’s not all. Let’s start with what you’ve seen before.

iWoman 1.x basically consisted of just one table view what showed the cycles. That’s still there right at the heard of the app. But the colors and overall design are more visually pleasing.

Periods are still being entered the same way as before by pushing the Plus button at the top. If you tap on one of the cycles you get the cycle detail view.

You see that here we have a nice tapestry in the back and the individual days are now showing three kinds of smiley to signify certain symptoms.

In addition to this list view there are now two different kinds of view added that serve distinctly different purposes. One that many women have requested is to have a monthly calendar view. You can get to that via the “Month” button.

Besides of giving a monthly overview the calendar view is the place where you manage events and facts on a daily basis. You see the menstruation days marked with a drop of blood and the calculated fertile days marked with a green sprout. If you tap on the row for a menstruation day you get to the symptom details for this day. By tapping on the blue accessory button you see the detail for the whole period.

There is a new memo feature that lets you record freeform notes for every day. That’s also included for free. Then there are two more tools useful on the individual days: intercourse tracker and basal temperature tracker. Those are available via In-App-Purchase. The temperature tracker has a beautiful mercury thermometer to input temperatures. The intercourse tracker lets you rate the sexual encounter, choose a partner and specify whether a contraceptive was used. The purchasing numbers of these features will tell me which to develop further.

The third major screen is what I call “the Wheel”. It’s aim is to give an overview over the cycle and show with a clock hand in which phase the user is currently in. As far as I know this is totally unique for apps in this genre. You can rotate the center circle with your finger and the calendar in the lower left corner will tell you which day your are pointing to. This way you can go a couple of periods into the future to get a feeling which phase will occur on certain dates.

On iWoman 1 I had a view like this on the startup screen and quite a few requests where for a screen like this. But I did not want to just have a static image in the documentation. Instead I wanted to give something to play with something that shows how YOU are.

The wheel control is reused in one of the settings screens where you can choose how many past periods are to be used for calculating the fertile days window. When testing with live data I found that there is a certain volatility in cycles lengths if you record them for like 2 years. The basic Knaus-Ogino algorithm would then cause the fertile days to take up half of the cycle. So I let you specify to use like 6 past cycles to show are more up to date picture. Using more cycles increases the security. This way users can specify what’s more important to them.

The most important feature probably is the passcode lock, also available via In-App-Purchase. If you are indeed recoding sexual encounters or your cycle you will probably be able to lock the app from spying eyes. With the passcode lock you can.

Many of the components that I built into iWoman have already proven their worth in other people’s apps. This marks the first time that all of these come together in a single product: DTCalendarView, DTPurchaseButton, DTCustomSwitch, DTNotePadViewController, DTPinLockController, DTAboutViewController and DTChartView.

I am very excited to have iWoman 2.0 out on the app store before Christmas 2010. I promise to you that I have a renewed sense of duty to keep improving iWoman, so please let me know if you have any kind of suggestions or feedback for me.