-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Design Committee #356
Comments
Hi UX Committee! Just confirming that all changes required from the document have now been implemented into the shop & inventory features. Thanks! |
That's amazing! We saw the improvements! Thank you for an excellent cooperation! |
Discussion between design committee members on the 13/10 about the scope of the Design Committee (i.e. whether it would enforce only style consistency or both style consistency and design cohesion) and whether style consistency would be a self checking process or not. It was concluded that design cohesion, whilst the eventual end goal, was outside the scope of this committee as it really depends on the user testing and research conducted by individual designers regarding their own designs. Style consistency, however, can be enforced and it was decide that this would be a self checking process and hence no submission folder was needed where designers would submit their work for approval. Decision relayed to all designers in the uiux committee: |
Description
Currently there are inconsistencies in the designs of different objects and UI elements in the game so it would be beneficial to all teams' designers to have a list of consistent guidelines. The purpose of the UI/UX design committee is to communicate results from team 15’s user testing, in which users will provide feedback on the design consistency and overall aesthetics of the entire game.
Dependencies
The communication of updated design guidelines and high priority design amendments will depend on the user testing and analysis completed by team 15: Improving UI elements and adding animations
Milestones
Completion Deadline: Oct. 18
Documentation
Members
The text was updated successfully, but these errors were encountered: