One thought on “First Project Wireframe–“Food Solo” Jackie(Yueyin Hu)”
We talked about some of this in class, but to reemphasize: it’d be very helpful if you labelled your wireframe views to match what you’ve documented in your app map. Also, the biggest thing is bringing back in your idea about generating music from the food you actually consume. Right now, it feels like you’re just associating sounds with foods visually, but the app would feel more interesting and rich if you add back in the recording of the food I’m eating. So, how do you make it obvious to your user that this is how they’re supposed to use the app?
Ideally your app won’t need on boarding views to teach a user how to use it. Try making your interface very clear first, and then we can add those in if completely necessary.
Likewise, it doesn’t seem necessary to have an account with your app. The phone can save all of the data locally, and the account doesn’t seem to be adding value. In general, we want sign up to be optional and not to be required at the beginning of the app flow if at all possible. You want to reduce barriers, and if you have a sign up/in at the beginning, a not small amount of users will abandon your app.
The interface to input my foods needs more thought. If that is just a flowing screen of foods, how do I find the one that I actually ate to input? Also, the dragging interaction is likely not going to be obvious to users. This is something that we could potentially prototype though with your digital prototype, if you end up wanting to try it.
Also with your digital prototype, you should probably test the actual music that will be produced by the app in some fashion.
In general, I think you’ll want to focus more on the creation and listening experiences. Saving things and going back to them and sharing seems less important, so make sure that you have the creation and first time listening set and then move on to other areas.
We talked about some of this in class, but to reemphasize: it’d be very helpful if you labelled your wireframe views to match what you’ve documented in your app map. Also, the biggest thing is bringing back in your idea about generating music from the food you actually consume. Right now, it feels like you’re just associating sounds with foods visually, but the app would feel more interesting and rich if you add back in the recording of the food I’m eating. So, how do you make it obvious to your user that this is how they’re supposed to use the app?
Ideally your app won’t need on boarding views to teach a user how to use it. Try making your interface very clear first, and then we can add those in if completely necessary.
Likewise, it doesn’t seem necessary to have an account with your app. The phone can save all of the data locally, and the account doesn’t seem to be adding value. In general, we want sign up to be optional and not to be required at the beginning of the app flow if at all possible. You want to reduce barriers, and if you have a sign up/in at the beginning, a not small amount of users will abandon your app.
The interface to input my foods needs more thought. If that is just a flowing screen of foods, how do I find the one that I actually ate to input? Also, the dragging interaction is likely not going to be obvious to users. This is something that we could potentially prototype though with your digital prototype, if you end up wanting to try it.
Also with your digital prototype, you should probably test the actual music that will be produced by the app in some fashion.
In general, I think you’ll want to focus more on the creation and listening experiences. Saving things and going back to them and sharing seems less important, so make sure that you have the creation and first time listening set and then move on to other areas.