Skip to content

ChicoState/ux-GoodDays

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

31 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

GoodDays

GoodDays enables users to keep a digital journal of their recent activities. By desinging a desktop journaling app we try to aid our users in reflecting on their days and personal habits.

UX Team Members

  • Max van der Veen - !!!List of Person A's primary contributions!!!
  • Nicolas Gres - Executive Summery, Heuristic Evaluations (part of the table), Figures, References
  • [Person C](!!!URL to Person C's published portfolio!!!) - !!!List of Person C's primary contributions!!!

User-Centered Design Artifacts

Phase I: Analyzing Users, Competitors, and Initial Designs

Executive Summary

Our research on the GoodDays journaling app highlighted the demand for free, minimalist journaling software.

  • Competitive Analysis identified a market gap for a minimal desktop application tailored to journaling.
  • Heuristic Evaluation of a custom Notion board revealed the following insights:
    • 🟩 Visibility of moods: A colored overview of recorded moods throughout the days would be extremely beneficial.
    • ▶️ Easy selection of actions: Loggable actions should be easy to identify and customizable during the journaling process.
    • 🛟 User guidance on journal creation: Integrating tips on the journaling process can be critical for newcomers.
  • Personas and Scenarios highlight the diverse user group interested in journaling.
  • Our initial sketches focus on mood visualization and the journal entry creation process.

Full phase I report

Phase II: Refining interaction and designing wireframes

Executive Summary

  • We started by making our initial wireframes
  • We used a cognitive walkthrough to gather in-depth feedback from other UI/UX students
    • Our wireframes felt incomplete. We had focused too much on the main screen, and not enough on the other screens
    • However, users really liked the main screen, giving us a good idea of how to proceed
  • The software engineering team also gathered informal feedback on their prototype
  • We then refined our wireframes with the feedback in mind, and made them interactive
  • Ultimately, we gave the software engineering team a much clearer idea of what to implement and how

Full phase II report

Phase III: Prototypes and User Testing

Executive Summary

  • !!!In a bullet-list, provide a summary that highlights...!!!
  • !!!What you've done during this phase...!!!
  • !!!and what the significance of it is...!!!
  • !!!as an executive would understand.!!!

Full phase III report

About

No description, website, or topics provided.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published