Love your graphic style. Very cute, reminds me of Saturday morning cartoons. Warm, fuzzy feeling. However, the icon is a little too cluttered and does not represent your app well in a first-impression sense.
How are you representing the critical path?
Some minor issues. 1) Since the Food Gantt chart is displayed landscape, not intuitive that you have to swipe left to go back to the main recipe list. 2) If you are scrolled way down on a Food Gantt chart and go back to the main recipe list and choose another one - the newly selected recipe is at the same scroll offset as the previous (e.g. already scrolled way down).
Suggestions. 1) Show the timer on the Gantt charts - e.g. simple moving forward animation (blink the time remaining for the X cooking step). 2) The standalone timer is a little hard to use and maybe too cutesy - a standard digital timer might work better but might not fit with your aesthetics 3) Social. If you can work out a deal with a cooking website (structure it as win/win - they get an iPhone app, you get the recipes) - you can seed your database in a hurry (I assume the custom graphics for ingredients would max out or could be genericized for the time being). 4) Judging solely on the app size (14.2mb), it appears that you may not be rendering the Gantt charts (e.g. they are drawn by hand? which is why you don't have timer integration). If this is true, this is your critical path - you need to render the Gantt charts as soon as possible.
How are you representing the critical path?
Some minor issues. 1) Since the Food Gantt chart is displayed landscape, not intuitive that you have to swipe left to go back to the main recipe list. 2) If you are scrolled way down on a Food Gantt chart and go back to the main recipe list and choose another one - the newly selected recipe is at the same scroll offset as the previous (e.g. already scrolled way down).
Suggestions. 1) Show the timer on the Gantt charts - e.g. simple moving forward animation (blink the time remaining for the X cooking step). 2) The standalone timer is a little hard to use and maybe too cutesy - a standard digital timer might work better but might not fit with your aesthetics 3) Social. If you can work out a deal with a cooking website (structure it as win/win - they get an iPhone app, you get the recipes) - you can seed your database in a hurry (I assume the custom graphics for ingredients would max out or could be genericized for the time being). 4) Judging solely on the app size (14.2mb), it appears that you may not be rendering the Gantt charts (e.g. they are drawn by hand? which is why you don't have timer integration). If this is true, this is your critical path - you need to render the Gantt charts as soon as possible.