Building positive habits that last for a lifetime.
Embedded Files
Team
Backend
Jin Myung | Grace Newman | Jason Yun
Frontend
Kimberly Ng | Fei Teng
Sponsors
Zachary Little & Ariana Witt
Development Process
Our team's development process focused on three main elements.
1. Weekly meetings with our sponsors
Every Wednesday night, we met for one hour on Google Meet with our sponsors. During these meetings, we would discuss the week's work, the sprint's progress, and goals for the next development period.
Our sponsors primarily gave us ideas to implement, as we had no preexisting code coming into this project. They ultimately approved any design decisions we proposed.
2. "Vertical slices" of development
Zach, one of our sponsors, emphasized the importance of this type of integration, where frontend and backend teams complete their own portions of the same features simultaneously.
Initially, our frontend team worked much more quickly than our backend team. But eventually, development became almost seamless between the two.
3. Pair programming and code review
Especially on the backend team, pair programming and code review were powerful tools to work through bugs and develop features more quickly.
Weekly stand-ups helped keep us accountable to each other. However, we maintained a positive attitude as a team, even during slow development periods.
Documentation
Low-Fi Prototype
Low-Fi Prototype
Mid-Fi Prototype
Mid-Fi Prototype
Hi-Fi Prototype
Hi-Fi Prototype
Trello
Trello
Our Trello board helped us organize and assign tasks between frontend and backend teams. Each Sprint, we created one card per action item, organized by team and priority level.
Our product backlog was maintained and updated each week after meeting with our sponsor and reassessing our trajectory.
Figma
Figma
Figma housed all our frontend design work. From low-, mid-, to hi-fi prototypes, we created and stored every version of Centurion here. This helped us see our design changes over time, allowing us to take the best elements of each iteration forward.
AWS
AWS
AWS Amplify was our backend framework, Cognito managed our user authorizations and logins, and we used DynamoDB for cloud-based storage of user data.
GitHub
GitHub
We used GitHub for version control of all files outside of the AWS environment!
Evaluation
Because our product was built from scratch, we were only able to start user testing toward the end of the second quarter of this Capstone project. We tested our app primarily on accessibility and intuitiveness, with a variety of age ranges. Because Centurion Movement is marketed toward people interested in longevity, we wanted to assure that the app was easy to use, regardless of technological literacy.
We found that users quickly picked up on the purpose of the app, and it was easy for them to understand how to input data. Our test group found that placing headers on input sections that matched the pages where they were displayed helped usability (e.g. Metrics input data is displayed on the Metrics page).
Final Product
Landing Page
This is the page that a new or signed-out user will see upon opening the app. We used graphics from our sponsor to design this page.
Home Screen
This is the first screen that a user sees after logging in or continuing as a guest. Any programs that they have subscribed to will be shown here, along with progress bars for each habit within the program.
Additionally, users can enter their metrics for each day, which includes weight, nutrition info, and calorie intake and output.
Metrics Page
We developed this page with the Weight Management program in mind, at the request of our sponsor. Users can see their long-term calorie intake and output, as well as body weight data. Users can hold down on any point in the graph to see the data points specific to that date.
Each graph features a dotted "average" line, so that users can see their progress over time.
Profile Page (with TDEE entry)
This page allows the user to see data about themselves, which includes email, name, and profile picture at this point.
Users can also input metrics to calculate their total daily energy expenditure (TDEE), which will update the calorie recommendations on the Metrics Page.
Page updated
Report abuse