Schedule
This is the main schedule for the term. Lectures are meant to be watched before class.
Class time is spent these ways:
- in-class lecture means that the instructor will lecture in-person (first week only).
- working indicates class time for you and your team to work together.
- demo is a working session with a short, informal demo with your TA.
- presentation indicates a longer, formal presentation to your TA.
1. Introduction
Getting started in the course! Forming project teams, managing projects and product requirements. Common development practices.
| Week | Lectures | Wed | Fri |
|---|---|---|---|
| Week 01 | Welcome, Teamwork, SDLC, Requirements | in-class lecture | in-class lecture |
| Week 02 | Kotlin Programming | working | demo |
| Week 03 | Architecture & Design, Build Systems | presentation 1 | presentation 1 |
2. Front-End Development
Client-side development; desktop and mobile applications. Building user interfaces.
| Week | Lectures | Wed | Fri |
|---|---|---|---|
| Week 04 | Desktop Applications, Compose Multiplatform | working | demo |
| Week 05 | Android, Navigation | working | demo |
| Week 06 | iOS, Kotlin Multiplatform | presentation 2 | presentation 2 |
3. Common Concerns
Common concerns that apply to both front-end and back-end; intermediate layers.
| Week | Lectures | Wed | Fri |
|---|---|---|---|
| Week 08 | Testing, Dependency Injection | working | demo |
| Week 09 | Data Classes, Serialization | working | demo |
| Week 10 | Concurrency | presentation 3 | presentation 3 |
4. Back-End Development
Back-end systems: databases, and services.