Requirements
- Find UI page designs here
- Design page from the last milestone. We have page drawings and detailed feature/ routing descriptions here
- Feature 1.8.1: The system shall be able to display markers in flown location.
- Feature 1.8.1.1: The user shall be able to touch a marker to get a popup of the marker.
- Feature 1.8.1.1.1: The system shall display the title of the marker in the popup.
- Feature 1.8.1.1.2: The system shall display the county of the marker in the popup.
- Feature 1.8.1.1.3: The system shall display the distance of the marker in the popup.
- Feature 1.8.1.1.4: The system shall display the favorites icon (heart) of the marker in the popup.
- Feature 1.8.1.1.5: The user shall be able to touch a marker's popup to go to marker's details page.
- Feature 1.8.1.1: The user shall be able to touch a marker to get a popup of the marker.
- Feature 1.8.2: The system shall be able to display user's current location with a person icon.
- Feature 2.2.1: The user shall be able to filter by Nearby
- Feature 2.2.1.1: The system shall be able to get the users current location
- Feature 2.2.1.2: The system shall be able to find the distance from current location to markers.
- Feature 2.2.1.3: The user shall be able to specify the range of markers they consider ‘nearby’
- Feature 2.2.2: The user shall be able to filter Wishlist
- Feature 2.2.2.1: The system shall be able to query Firebase to get a users wishlist
- Feature 2.2.3: The user shall be able to filter by their Markers
- Feature 2.2.3.1: The system shall be able to query Firebase to get a users visited markers.
- Feature 2.2.4: The user shall be able to filter by County
- Feature 2.2.4.1: The system shall display a drop menu of all the counties
- Feature 2.2.4.1.1: The user shall be able to select a county from the drop menu
- Feature 2.2.4.2: The system shall be able to query Firebase to get all markers from a specific county
- Feature 2.2.4.3: The system shall indicate if the marker is visited or not
- Feature 2.2.4.1: The system shall display a drop menu of all the counties
- Feature 2.3.1: The system shall be able to recommend predicted searches before completion
- Feature 2.3.2: The system shall be able to look up keywords in descriptions
- Feature 2.3.3: The system shall be able to look up keywords in name
- Feature 2.3.4: The system shall be able to look up by location
- Feature 2.4.1: The user shall be able to see the marker on the map
- Feature 2.4.2: The system shall display the distance from the user to the marker
- Feature 2.4.3: The system shall display the marker description to the user
- Feature 2.4.4: The user shall be able to add a marker to their wishlist (heart icon)
- Feature 2.4.5: The user shall be able to click “Take me There” to route to the marker
- Feature 2.4.5.1: The system shall redirect to PLAN ROUTE page
- Feature 3.1.1: The user shall be able to authenticate with a username.
- Feature 3.1.2: The user shall be able to authenticate with a password.
- Feature 3.2.1: The system shall fetch user name.
- Feature 3.2.2: The system shall fetch user id.
- Feature 3.2.3: The system shall fetch user biography.
- Feature 3.2.4: The system shall fetch user friends.
- Feature 3.2.5: The system shall fetch user favorite marker list.
- Feature 3.2.6: The system shall fetch user marker wish list.
- Feature 3.3.1: The system shall create a unique user id.
- Feature 3.3.2: The system shall store user specified username.
- Feature 3.3.3: The system shall store user specified biography.
- Feature 3.3.4: The system shall create a dummy marker wishlist.
- Feature 3.3.5: The system shall create a dummy markers visited list.
- Feature 3.3.6: The system shall create a dummy friends list.
- Feature 3.4.1: The system shall store unique user id.
- Feature 3.4.2: The system shall store user specified username.
- Feature 3.4.3: The system shall store user specified biography.
- Feature 3.4.4: The system shall store marker wishlist.
- Feature 3.4.5: The system shall store markers visited list.
- Feature 3.4.6: The system shall store friends list.
- Feature 3.5.1: The system shall store the marker name.
- Feature 3.5.2: The system shall store the marker relative location.
- Feature 3.5.3: The system shall store the marker description.
- Feature 3.5.4: The system shall store the marker GPS coordinates.
- Feature 3.4.5: The system shall store the marker county.
- Feature 4.1.1: User can click on Account Profile Picture to go to Account page
- Feature 4.1.2: User can click on HOME to go to home page
- Feature 4.1.3: User can click on MY MARKERS to go to MY MARKERS page
- Feature 4.1.3.1: System shall display all counties in SC
- Feature 4.1.3.2: System shall display relevant icons above each county
- Feature 4.1.3.3: System shall display the ratio of visited markers to all markers within each county.
- Feature 4.1.3.4: System shall redirect to MARKER LIST when a county is clicked
- Feature 4.1.3.5: System shall query the clicked county from FireBase
- Feature 4.1.4: User can click on PLAN ROUTE to go to PLAN ROUTE page
- Feature 4.1.4.1: System shall detect users current location
- Feature 4.1.4.2: User shall be able to use current location as starting point
- Feature 4.1.4.3: User shall be able to specify marker as endpoint
- Feature 4.1.4.4: System shall be able to find shortest path from start to endpoint
- Feature 4.1.4.4.1: System shall be able to find shortest walking path
- Feature 4.1.4.4.2: System shall be able to find shortest driving path
- Feature 4.1.4.4.3: System shall be able to find shortest public transportation path
- Feature 4.1.4.5: User shall be able to add custom routes.
- Feature 4.1.5: User can click on WISHLIST to go to WISHLIST page
- Feature 4.1.5.1: System shall redirect user to MARKER LIST
- Feature 4.1.5.2: System shall query the users wishlist from FireBase
- Feature 4.1.6: User can click on FRIENDS to go to FRIENDS page
- Feature 4.1.7: User can click on ACCOUNT to go to ACCOUNT page
- Feature 4.1.8: User can click on HELP to pull a brief tutorial on how to use the app.
- Feature 4.1.9: User can click outside of the menu to exit the menu bar.
- Feature 4.2.1: The system shall display the username of the user.
- Feature 4.2.2: The system shall display the markers visited by the user from the total.
- Feature 4.2.3: The system shall display user profile image of the user.
- Feature 4.2.3.1: The user shall be able to click on the profile image to go to the Account page.
- Feature 5.1.1: The user shall change their profile image by clicking the profile image to display a popup.
- Feature 5.1.1.1: The user shall be able to pick to take a new image.
- Feature 5.1.1.2: The user shall be able to choose an existing image.
- Feature 5.1.2: The system shall access the user’s camera to take a new profile image.
- Feature 5.1.3: The system shall access the user’s images to pick a new profile image
- Feature 5.4.1: The system shall check that the users biography is less than 500 words
- Feature 5.5.1 The system shall notify a user when they have a friend request
- Feature 5.5.2 The system shall notify a user when they reach a new marker.
- Feature 6.3.1: The system shall give a description of each button.
- Feature 6.3.2: The system shall give a description of each page.
- Feature 6.3.3: The system will ask the user to interact with the buttons.
- Feature 6.3.4: The user can skip the interaction with a skip button.
- Feature 6.3.5: The user shall be able to skip the whole tutorial at any point in the tutorial.