Gamified Todo - cs428TAs/w2024 GitHub Wiki
- Jacob Brown
- Zachary Driskill
- Kaden Klein (person who pitched idea)
- Tyler Pearson
- Julia Routh
- Kenneth Salomonson
- Weston Smith
Basically a simple web app that makes it easy to do a daily planning adding todos really simply and rewards you for completing your todo's for the day. It will need lists to complete for each todo, and a fun interface that is super simple and easy to set up to be used daily. Hopefully add some reminders as well to get good habits going.
More Details
- Flask/Python
- Java android app
Tasks vs Reoccuring tasks (habits)
- Name
- Date to complete by / when it occurs
- Importance/Difficulty level --> Points
Different lists/groups of tasks
Game part To do list ------> Points -----> Game\n
Notifications
- manual
- jetbrains
- notion
- trello board
- Status Report 2/3/2024
- Status Report 2/10/2024
- Status Report 2/17/2024
- Status Report 2/24/2024
- Status Report 3/1/2024
- Status Report 3/9/2024
- Status Report 3/16/2024
- Status Report 3/23/2024
- Status Report 3/30/2024
- Status Report 4/13/2024
Org Chart and Role Descriptions

The Gamifiy ToDo App will be broken into 3 teams: Management Team (project manager and chief architect), Front End Team, and Back End. The connection between all will be Quality Assurance to ensure proper testing done in both ends of the product.
Project Manager: Julia Routh
- Handle tasks and planning for each team
- Works with Chief Architect to prioitize features and keep the project on schedule
- Handle status reports at the end of each week
Chief Architect: Kaden Klein
- Final word on design decisions and implementations
- Responsible for creating a conherent design that maintains conceptual integrity
Quality Assurance: Kenneth Salomonson
- Create test plans for front and back end
- Implement unit, integration, and system testing
- Ensure there is no technical debt (ex coding standard)
- Communicate with both ends and Chief Architect to make system parts easily integrateable
Front End: Jacob Brown and Tyler Pearson
- Responsible for the design and implementation of mobile application
- Coordinates with Back End about the availability of API's to populate data
Back End: Weston Smith and Zach Driskill
- Responsible for the implementation of a web server to populate our mobile front end with data
- Communicate with Chief Architect to create correct API's for front end
User account
- login and credentials
- that keeps track of habits and todos stored in a database
Notifications
- daily planning
Add new habit -name -due date -reoccurring
Reward System
- Complete a task and get a reward
- difficulty level (attached to amount of points you get)
- Betting system
Game Both:
- Create Game save Object
Game (Adventure)
- Get loot and items from points
- Adventuring gets you XP
- You need both to progress
- Viewable UI
- Login page with working user
- Authorization and authentication of user
- Create and store new items in database (SQLite)
All objects:
-
Task: task name, difficulty, due date, recoccuring, create, update, delete
-
Player: character name, level, points
-
User: username, password, userID
-
Spending points in game
- All types of tasks and their features are functional
- Notifications for daily planning, due dates, recoccuring tasks
- Basic leveling up for game
- Single level in game
Full game functionality Finished ui
- Friends
- Subtasks
Pert Chart (img)

Preliminary Architecture
