Schedule
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, Build Systems, Testing | working | check-in |
| Week 03 | Architecture, Design | demo 1 | demo 1 |
Front-End
Client-side development; desktop and mobile applications. Building user interfaces.
| Week | Lectures | Wed | Fri |
|---|---|---|---|
| Week 04 | Desktop Applications, Compose Multiplatform | working | check-in |
| Week 05 | Android, Navigation | working | check-in |
| Week 06 | iOS, Kotlin Multiplatform | demo 2 | demo 2 |
Middle-Tier
Concerns that apply to both front-end and back-end; intermediate layers.
| Week | Lectures | Wed | Fri |
|---|---|---|---|
| Week 08 | Data Classes; Serialization | working | check-in |
| Week 09 | Concurrency | working | check-in |
| Week 10 | Dependency Injection | demo 3 | demo 3 |
Back-End
Back-end systems: databases, and services.
| Week | Lectures | Wed | Fri |
|---|---|---|---|
| Week 11 | Data Persistance | working | check-in |
| Week 12 | Web Services | working | check-in |
| Week 13 | Security & Packaging | demo 4 | demo 4 |
Legend
Lecturesare normally recorded and posted online, and should be watched before class. Aquizis a graded assessment that follows the lecture.in-class lecturemeans that the instructor will actually lecture (first week only).workingindicates scheduled time for you and your team to work on your project. Attendance is not required.check-inis a working session, where your team is expected to discuss progress with your TA. Attendance is required.demoindicates a formal demo, where you will present your project to your TA. See the demo schedule for format and time.