-
Notifications
You must be signed in to change notification settings - Fork 0
Feedback
find available locations for volleyball
- user could easily locate volleyball locations
view location of any park
- user could easily zoom in and find location from pin. Would like to have the view auto-align and zoom to a fitting view when clicked.
What do you think about the chosen maps and its colours?
- I feel familiar with the chosen map, as it is one which is often used in applications. I can easily distinguish land from sea, which is not often the case with maps. I feel like the markers have a good contrast and are easily visible. I do not understand why I am being served with road information, as I am against the use of cars and only use roads for biking/walking. Would much rather see landmarks so that I can navigate easily.
What do you feel about the amount of information you are given in the map?
- Answered in previous question
What (if any) other map views would you like to have?
- I would like to have the option to switch to satellite map, as when I try to locate a park based on the map I find it difficult without using references from satellite images. It makes it easier to find paths and smaller roads I can use.
What do you think about the filter menu?
- Works nicely, I understand the horizontal scroll. It might be a problem if it aligns perfectly so that there is no clear indication to the user that there are more buttons to the right. Maybe it would be better with an indicator such as an arrow?
What if anything do you feel is missing for navigation?
- I would like to have the map zoom and fit to a point when I click on a location, and for there to be displayed information.
What information would you immediately want for evaluating location?
- The most important is to understand that I am looking at the right type of location. I want to see images of the park, and a description of how you would arrive there. I want to know which equipment is available.
Erlend liked the emoji menu as he feels it really speaks to him as a person who grew up in the emoji age. He feels that it make the app younger and more fun, which is what he wants from the application.
Some pointers:
- Keep the app to be only map usage, no search or location via text.
- Sort the categories based on most popular categories. First app-wide, then adapt to user.
- Task: How do you create a desire to add locations?
- Send back location adds to user and make them do the necessary updates for approval
Make it easy for new people to join the project:
- Name of functions and methods need to be standardised and understandable
- Reduce complex code
- Think as a fresh developer
- Define patterns to follow (max length of file, DRY)
- Decide together how the code-etiquette should be
- No unnecessary comments, code should be self-explanatory
- Methods/Functions should have verb as first part of name
- No Method/Function calls inside Method/Function calls. Define as return value as variable, then use in function.
View information about the locations, both with the "teaser" and with the full information card.
When would you choose to use the close icon in the popup window?
- Icon is the only way to go
Where do you want to return to when re-entering map from information page?
- No information when returning, I feel I'm done with the point when exiting.
- More padding in the navigation buttons top and bottom
- Take back mini popup when clicking on other locations
- Look at what google map does with zoom and locations
- Indicate that there are more photos in the application (half-blur on the other side)
- Rating should be given using the stars on top of the information page
- Change colour on popup start to be black
- Remove the information when user slides down, and give the teaser to the user
- If we use infinite scroll, we need a button to return up
- Categories instead of Category for API
- Use Material UI with Figma to test out layouts
- Contact Fredrik W, he has cool method for automatically convert backend types to typescript types.
- Look into typeguards, for checking that types are actually what you want
- Error handling is important, handle errors when you make an API call. SnackBar is the way!
- Error Boundary. Catch error/crash and display to user.
- Try/Catch for all api calls
- Interceptors in Axios
- Application insights. Owner wants to know about the traffic. Needs to be implemented in frontend.
- GitHub Actions
Functionality to add park locations