See also: GradingGrading
See also: Syllabus · Lectures
Tech 1 Grading Plan
Assessment and Grading Breakdown
#
Component
Weightage (%)
1
Attendance and Class... · Exercise - Final Project IdeasExercise - Final Project Ideas
Start collecting ideas for your final project
Your final project is a startup: a digital product that people sign in to and use, and a landing page that tells them about it and lets them sign up. ...
Brief
In teams of up to 3, start a startup. You'll make two things:
- A digital product that people sign in to and use. It can have AI features, but it doesn't have to.
- A landing page that tells people what your product is, lets them sign up, and takes them straight into using it.
Both are deployed, built mostly by directing AI tools, and presented at Demo Day.
The shape of it
- Introduced (L9, 13 October): the brief, and what a startup is. Sharpen your ideas.
- Kickoff (L10, 27 October): form teams, pitch ideas, submit a one-page proposal: the problem, who it's for, the core flow, and a sketch of your stack.
- Sprint 1 (L11, 3 November): sign in and the core flow working end to end, however ugly. Live crit.
- Sprint 2 (L12, 17 November): the landing page, and the product made ship-ready: empty and error states, a security check, polish. Feature freeze at the end of the week.
- Demo Day (L13, Friday 27 November, from 2:15pm): a 7-minute live demo, starting from your landing page, plus your process story, and 3 minutes of Q&A.
Requirements
- Deployed and public. A URL that works on a phone on the day of the demo.
- Sign in. People sign in to use the product, with Sign in with Google or another provider, as in Lecture 8 - Authentication & Authorisation Note does not exist
This note is has not been published (yet).
and Exercise - Sign in with GoogleExercise - Sign in with Google
Add Sign in with Google to your multiplayer experience
Take what you built in Exercise - Realtime Web Experience and make people sign in with Google before they can change anything. Same Fireb.... Your database rules use it, so people can only change their own things. - Has a back-end. It stores or fetches real data: a database, an external API, or both.
- A landing page that:
- says what the product is and who it's for, in the first screen
- shows the product, with screenshots or a short video, not just describing it
- has one clear sign-up button that leads into the product
- works on a phone
- The first five minutes are designed. Landing page → sign up → first use is one flow. What does someone see the first time they sign in, before they've added anything?
- Process documentation. Your proposal, sprint plans, prompt logs, dead ends, and what you'd do differently.
- You understand your stack. Every team member can answer "where does this data live?", "what happens when I click this?" and "how does the app know who I am?"
An AI feature is welcome if it earns its place, but it's not required.
Scope advice
The best projects are one small thing that fully works. "Splitwise for hostels" beats "a social network." You will cut scope in L11. Teams that pick a small idea get to spend L12 on the landing page and polish instead of fixing things.
A startup needs people who'll actually sign up. Pick a group you can reach this month, and get a few of them to sign up before Demo Day.
Evaluation
| Criteria | Marks | Description |
|---|---|---|
| Timeliness | 2 | Proposal and sprint milestones hit on time. |
| Concept | 3 | Clarity of the problem, fit of the solution, sensible scope. |
| Working Product | 5 | Deployed, sign-in works, core flow works, handles errors, works on mobile. |
| Landing Page & Sign-up | 3 | Explains the product clearly, and takes a stranger from first visit to using it. |
| Design & Polish | 3 | Visual quality, states, coherence: the design work AI skips. |
| Stack Understanding | 2 | The team can explain how their own product works, at this course's depth. |
| Presentation & Process | 2 | Demo quality, and honesty and completeness of process documentation. |
| Total | 20 |