From solving current design problems to ideating on possible new features the purpose of this ticket is to develop a resource or a guide that would be used by all designers despite their focus area. The concept is evolved around the need to introduce guidelines specific enough to be acted as a checklist/criteria for designers when confirming their design's consistency. This ensures that every designer reduces time needed to get feedback. Furthermore, from design cohesion perspective these guidelines will help with the verification on whether the design fits into the game overall style direction.
Example of usage
Design Style: guidelines that can be used by other designers to "self verify" the design direction for the Atlantis Sinks game.
Design cohesion: explanation on how to verify whether the design fits into the game based on the overall theme of the game
Dependencies
Following tickets will be used as references to support the documentation and the creation of the final guide.
Description
Task: Design Style and Cohesion Guidelines by Team 15 Feature: Improving UI elements and adding animations
From solving current design problems to ideating on possible new features the purpose of this ticket is to develop a resource or a guide that would be used by all designers despite their focus area. The concept is evolved around the need to introduce guidelines specific enough to be acted as a checklist/criteria for designers when confirming their design's consistency. This ensures that every designer reduces time needed to get feedback. Furthermore, from design cohesion perspective these guidelines will help with the verification on whether the design fits into the game overall style direction.
Example of usage
Dependencies
Following tickets will be used as references to support the documentation and the creation of the final guide.
UI Style Guide Design Guidelines Building UI Overview Target Audience Analysis Primary User Group Design Committee Research Overview of Juicy UI Map Design and Inspiration
Milestones
List of sub-features we intend to complete in the final sprint.
Completion Deadline: Oct. 18
Documentation
Team 15 Sprint 4 Members