We enlisted the advice from one of our course TAs, Laura, to gain yet another perspective about our app. We hoped to see if she had any general comments about how we could improve our implementation going from our Balsamiq implementation to this stage. To gain her insight, we visited her during one of her drop-in hour sessions and walked her through each iteration of our Balsamiq prototype in addition to some of our own concerns. Laura's comments: Get rid of the multiple time slots feature for those creating an event, as this leads to several confusing implications on the user’s end. Use a combination of tags for the cuisine preferences and an optional bio (rather than “interests” which is vague). This will give users varying degrees of freedom in expressing themselves, based on what suits their interests. Split up the handling of allergies versus dietary preferences (previously all lumped into the same category of dietary restrictions). For allergies, users may choose to flag or highlight restaruants that use their allergen when scrolling through their home page. For dietary preferences, users may choose to hide options that don’t match their dietary preferences when scrolling through their home page. It may be helpful for the group to have a statement such as, “Someone in this event has a nut allergy.” Don’t want to single out the users who have allergies, yet keeping the group informed may lead to a more mindful and comfortable experience for everyone involved, as other members of the group can choose to be more mindful of allergens without a long, drawn-out conversation about the topic. Even though we want to have a more social aspect, we can make the people shown more subtle For example, show the profile pic of the host and perhaps their name. It’s important to minimize the judgmental aspect that may arise in apps such as Instagram. Change the wording of the confirmation alert to make it clear that the user is requesting to join the event, rather than automatically joining it.