One thought on “DumpCook: Iteration1”

  1. While it might hurt my soul a little, I think there’s a huge market for the concept of your app, and it’s great that you have a clear user group that you’re targeting.

    I think it’s great to think through the things even at a top level that are going to help your users make the decision of what recipes to look at. I’m wondering if seeing 4 hours on something is going to turn off your user who want something simple even though 99% of that time is in a slow cooker? Maybe it’s worth separating out active and total time?

    Your tab bar is a bit unclear. Which tab am I on when I’m on 1.0 Recipes? Remember that if you have a tab bar, you always need to be in one of those tabs. Perhaps it makes sense to have a Recipes tab. What the chef’s hat circle button in the middle of your tab bar? Is that where I add recipes?

    The recipe filters seem to make sense, but you may want to think through the ‘exclude’ portion in a little more detail. Instead of making that free form, it might be worth giving defined options. This will probably be easier for users and be better for your data organization. You could have buttons will things to turn on/off.

    Is the only place I can add recipes in the profile view? But even before we consider that, do you really think that the folks that want incredibly simple recipes are going to be willing to take the time to put recipes? Perhaps, because you certainly find plenty of these recipes on Pinterest, but I wonder how many are original posts. You can argue it; just make sure that it’s fully thought through. You’ll also want to think through how to populate the app before anyone has posted to get people to start posting there in the first time or using the app at launch.

    I believe we spoke about this, but if you’re going to push the community aspect, then how to do you highlight publishers/cooks? Can I follow someone if I like what they’re posting? How often will someone actually post if they ever do?

Leave a Reply