uudaddy

Latest and the greatest

1) Fixed “data not being saved” bug in myNestEgg and collegeFund

2) Also, in myNestEgg v 1.5, we added “Auto Pilot” feature, similar to what has been introduced in collegeFund 1.5. The main difference is in myNestEgg I set income ratio to 70%.

Why 70% for income ratio in retirement
I briefly mentioned it on my personal blog, 70% is a magic number because I assume social security and other savings made up the rest (30%) of the retirement income.

(Update 05-13-2011) Released. Free for a limited time. Here is a link to the iTunes App store.

(Original) This is to address one problem posed by a user in the iTunes app store review. Basically his (her) comment is that the iteration approach (try and error to get desired coverage ratio) takes too much work.

I think the comment is a good one, and here I am making the “auto pilot” option available (the default is OFF). It works like this, in “setting”, the user turns on the “auto pilot” switch. In the “calculator” tab, when the user hits “calculate”, the user will have 80% coverage ratio, and the “saving annually” text field will have a value that achieves that 80% goal.

All proceeds from the sales of the myNestEgg and collegeFund (CF is free this week) apps between March 13th and March 27th will be donated to the Saving the Children for the disaster relief efforts in Japan.

If you prefer to make a direct donation to the relief efforts (you can probably get more bang from your bucks that way), Apple has set up a way for you to do it via iTunes here.

It’s that time of the year again, the time for new year’s resolution and planning. The past year has brought interesting addition to our family: our baby girl “Youyou”. On business (or iOS app) side, I joined the iPhone (iOS) developer program in July (paid the $99 annual fee), and released the first app myNestEgg ~ the retirement calculator in middle Sept. The second app collegeFund ~ college savings calculator shortly followed. The results exceeded my expectation, as I released a few updates to fix the problems/add features. Meanwhile, I went to the Voice That Matters – iPhone developer conference (Philadelphia) in Mid Oct. Meeting iPhone developers and learning new things are the main take aways there.

For the new year, I am thinking of two things: 1) Continue to improve the existing apps; 2) Work on an iPad version of retirement savings planner. I don’t have a definite timeline yet, as I still have a day job, but I hope to release the iPad app before the iPad 2 arrives.

This is to fix a show stopper problem in v 1.2, as pointed out by one of the users. The problem happened after a user used the keyboard to input data (dismiss the keyboard by tap background), the app will add a comma to “beginning savings” and “salary”. This causes confusion and mis-calculation down the road.

The problem is fixed now in v 1.3. The user needs to update the app to get the fix. In some cases you may need to re-enter the “beginning savings” and “salary” if those numbers are no longer correct in the app. Please let me know if you have any problem.

I am sorry for the inconvenience it may have caused, and wish all a good holiday.