Sprint 1: Minimal UI

There are many ways to get started on our implementation. We’re going to work top-down: we will design screens and workflows that reflect our requirements. We will do this by:

• Building low-fidelity prototypes of all of our screens.
• Implementing each of these prototypes in code, and adding scaffolding so that our application can display these screens.

Your UI is not expected to be functional yet. The goal is to have screens that you can demonstrate to your TA during the demo to get more feedback.

Requirements

For this sprint, you should complete the following:

• You should have low-fidelity prototypes from your proposal, and hopefully feedback from your TA.
• Iterate on your prototypes and make any suggested design changes.
• Implement these new desigins by:
  • Creating a View and ViewModels for each screen.
  • Writing Compose layouts for each View class.
  • Add a custom theme so that you have a consistent look-and-feel across all screens. Make sure to change some obvious details so that the TA knows that you didn’t just use the default colors!
• Add scaffolding so that your application can be compiled and executed. It needs to be runnable for the demo.

A user should be able to run your application and have it display the initial screen.

• They should be able to navigate between all pages of your application.
• You do not need to have “live data” but should “hardcode” data into your screens so that the user can see how they look.

Submission

After the demo, you will need to ensure that your work is complete so that it can be graded. This means that all documentation should be updated (issues, wiki pages, team meeting minutes), and all source code should be frozen (changes pushed, everything merged to main).

The deadline is 6:00 PM on the listed time and date. You do not need to actually submit anything; we will grade what is posted in your GitLab project at the deadline.

The content that is in GitLab should be the same as what you presented in-class. You are allowed to make small corrections but please avoid making major content changes between the demo and the submission.

Grading

The grading scheme is available in Learn under Resources > Rubrics.

Deliverables are normally graded by the following week’s lecture, and the grade and feedback will be posted under Submit > Dropbox. Any questions related to this should be sent directly to your TA.

See grading policies for more information.