Sprint 2: User Interface
⚠️
You should have received feedback during Sprint 1 demo; please make sure to address that feedback in this iteration!
The goal of your second iteration is to design and implement your user interface, including the basic structure and some of your screens. This will likely be an ongoing concern, and it’s expected that you will be iterating on your UI for the rest of the term. However, we expect you to start with the correct structure in place, know what your screens will look like (and how they are designed) and have some of these screens working. You should be thinking about the “polish” of your UI, but look-and-feel doesn’t need to be finalized yet.
Requirements
For this sprint, you should complete the following:
- Any remaining requirements from previous demos.
- Feedback from
Demo 1
should have been addressed. - You should have screen mockups i.e. low-fidelity prototypes of your screens. Figma is recommended, although they do not need to be interactive screens.
- You should have basic UI classes in place for at least two of these screens. This includes
ViewModels
wired up to yourModel
classes, andComposables
akaViews
for those screens. You are not expected to have all screens fully implemented at this stage; that will normally happen over the course of the last three iterations. - You should have a custom theme in-place, with at least a few elements changed from the defaults. All screens should use this theme.
- Other features as required to make reasonable progress on your application.
Grading
Component | Items | Marks |
---|---|---|
Project | The project builds and runs using ./gradlew from the command-line. |
1 |
Issues and project documents are up-to-date. | 1 | |
Features | Designs for all screens are complete i.e. Figma diagrams. | 1 |
Multiple screens have been implemented and are functional. | 2 | |
Screens are implemented as Views and ViewModel classes. State is hoisted out of views. | 2 | |
User can navigate between screens, using intended workflow. | 1 | |
Progress was made on custom or advanced features. | 1 | |
Unit tests exist for these features, and all tests pass. | 1 | |
Total | / 10 |