These pictures are user interface screenshots from Xcode showing real UI files which will run on the iOS platform. The idea is that other platforms shall replicate this design to the pixel.
We have established the main pipeline in which the user experience shall travel through. In order to include as many target groups as possible we wanted to keep the number of views and UI elements down to a minium without causing confusion. Therefore we went with one workflow/procedure and two main views.
First we have a main screen which is the general search view. This aims to eliminate which type of museum the user wants to visit. It can vary from art to ecologi.
This view shall be one of two consistent views. The other one is where your personal route is displayed. When not displaying a personal route that view shall redirect to this one, thus gently pushing the user towards making a new route. These two shall always be within one click.
This view is where the generated routes are displayed to the user after all the requirements are inputed. As it is right now the back buttons do not show but are included in our design so that the user can at anytime during the procedure go back and redo some of the inputs. They are also able to cancel the creation at anytime.
This is a rough mockup how a typical personal route might be displayed. The idea behind the map is to have a sort of slide up motion to bring the map into fullscreen. On the map itself the route is displayed with an option to hide/show it as an overlay. This is the second main view which shall always be present.