During the user test and final feedback interesting comments were made. In the home page the icon that goes to the list had the logo of the app next to it. So the two elements were the button. This proved confusing for the user, he thought they were to separate elements. So I just let the stripes that symbolize the list element.
Also at the end, I just realized that when shopping different items from different stores it will be better to have a pick up and delivery button in each item instead of having it at the end. We might be in a situation where I purchase 5 items from 4 different stores. So I want to have the possibility to select from which I want delivery or pick up. This is something to have into consideration for a further iteration.
Timehop is an iPhone app that once you log in with your facebook, twitter, instagram, and/or foursquare creates a time capsule of all your social media since you created it. Every morning you receive a new “time hop” that tells you what you did on that day exactly 1…2…3…4…years ago. This app has been fun in that sometimes I’m reminded of fun memories I had forgotten about and sometimes I’m reminded of how awkward of a high schooler/college freshman I was. The only improvements I wish this app would make would be 1. that it would show you other activity besides just status updates 2. that you could include older social medias for a longer time capsule like Xanga, MySpace, or Livejournal etc. and 3. that it would be available for Android 😉
Fridge is a recipe book based on the ingredients that are currently available in your kitchen… and by extension a grocery management system.
The concept arises from the problems in the flow of how i cook, and apparently it is a really common flow:
The aim of Fridge! [name in progress] is to eliminate that loop making cooking a less frustrating experience for the user. The way to achieve that is to rethink the flow and making it from the bottom up. Instead of looking for recipes we actually look for the ingredients that the user has and match them to a database that trows back the recipes that are possible to make.
Once the infinite resources that we have to make this app create create the database we can do more than just ask for what the user can cook, but suggest ingredients that the user can buy to expand the available recipes.
My first approach to this was overcomplicating the app trying to create a geofencing around the home of the user to change between functions and a tutorial. //
Thanks to the input of the testers and the various iterations of the app the final flow has a lot more functionality and creates a better experience for the normal vs the power user scenario.
My first set of mockups focused on a very specific element of my interface, i consider that the rest of the app was self explanatory but the filtering system required a lot of thinking and research. I was having really big issues with the amount of information that my app require to keep on screen in order to filter the recipes, and I’m not a huge fan of how Seamless fixed the issue. i found this patent and got interested on circular interfaces. There is a huge amount of reseal around circular interfaces, yet very few of them focus on mobile devices and the “self collapsing half circle” //the pattern that i used is really no show. My biggest inspiration was the circular editing interface of the new tablet microsoft office suite. and the experiments by the old Quicksilver.app developers.