There would be approximately 5-6 screens for the app. See below for details around each screen as well as mock-ups of each screen. Please note that the mock-ups that we have created are solely for illustrative purposes so feel free to use them as much or as little as you like / be as creative as you like with this.
Here is what we would like: Please make mock-up Screens #1, 3 (iv) - the Who Are We Telling screen described below - and #5. These are the essential screens that set the tone for the app and are the most difficult to imagine. If you can get those right, you can get the others right!
-Screen #1: Sign-In-- Fairly standards as pictured in the below mock-ups.
-Screen #2: Home Screen
-If user has not been invited to any events, the first screen will be a slightly animated Conch shell, bouncing up and down. Clicking on the Conch Shell takes users to Screen #3
-If a user has been invited or is hosting events, this screen should display any pending invitations / attending events (scrollable list) and any hosting events (also scrollable). Events should be sorted by time (earliest event first) and whether the user RSVPd (RSVPs first). Clicking on an event takes the user to the corresponding event page (Screens #5).
-Users can press the shell in the top right to “Sound the Conch”.
-Screen #3: Define the Event -- Screens will show up in the following Order: 'What’s the plan?' 'When's it happening?' 'Where are we going?' and 'Who's coming?'
-For this one, do either one of or all of these to give us a flavor of how you would approach the flow here.
-UI: Show a dial on the bottom left that indicates progress through the four screens.
-#3 (i) What's the plan screen: Users enter any name for the event (to-be-defined character limit imposed) as well as choose from a short list (or icon set, depending on design--see mock-ups) that defines the type of event it will be (e.g. Party, Go Out, Get Food, Study, Workout, Activity)
-#3 (ii) When's it happening screen: Allows users to select start and end time of the event.
-#3 (iii) Where are we going screen: Users type the location of the event. As they type, the auto-complete helps them locate / geotag the location, prioritizing addresses / locations that are nearest to the user’s current location. Upon selecting the location, the map shows a ‘pin’ on the location they selected so they can confirm that it is correct.
-#3 (iv) Who are we telling Screen: Users can either select people they invite in one of three ways: (i) by group (ii) everyone within a radius, or (iii) by selecting individuals. These are shown in an accordion list display that expands depending on the method chosen by the user (e.g. if user clicks by group, that section expands while the others remain collapsed).
-#3 (v) Summary Screen: This summarizes the contents of the other screens. If a user clicks any of the text boxes, they are taken to the corresponding screen to edit their response (e.g. if they click the When text box, they are taken to the When screen).
-Screen #4: Profile: Profile should include the user’s profile picture, name, email, phone and school. There is a button to log out / edit your profile.
-Screen #5: Event Invited / Attending Screen and Event Host Screen
-Hosts of events will see Event Host Screen, others will see Event Invited / Attending Screen. The only difference is ability to Edit event and ability to Add Hosts.
-Screen should display all information about the given event.
-Users should be able to toggle whether they are going or not.
(FUTURE)-Screen #6: Chat
-As additional users join, they see the full history of the chat. Everyone who RSVPs is allowed to see the chat. Messages are seen by everyone who RSVPs.
-Types of Messages: Users can type and send text-only messages in the chat. No photos, location pins, etc should be sent.