Love the updated “site map”! Great inclusion of feedback.

I’m wondering if having your itinerary accessible through two separate places might add confusion, or be a little more challenging to learn. This is something to test once you have a prototype (and we cover testing the class after midterms).

Consider the alternative options and think crititcally as to what will be the most beneficial to your user: Having the itinerary accessible at all times, or in one place (you can still have links elsewhere that lead to the itinerary, but it will only be nestled within the profile, for example).

The benefits of having it accessible at all times means your user can constantly be checking when their next activity is. This could be good if an important goal is user keeping track of events. The other alternative could benefit your user on a heuristic we briefly covered, consitency. Depending on your interface and how you create the path to the itinerary, not having the itinerary button in some places, but there in others could lead to difficulties remembering where to access it. In interface design it’s said that memory recognition is better rather than recall. For an amazing explanation https://www.nngroup.com/articles/recognition-and-recall/. This might sound counter to my previous point. The latter suggests that we should have clues to help the user recognize how to achieve a goal. This is where having the itinerary in mutiple places could be more beneficial. Therin lies the challenge to give those clues while still maintaining consistency!

Anyways, I’m rambling now. But things to keep in mind as your developing your interface and your UX senses!