Read before you start
Practical exam instructions
ENCE 216 — Mobile Computing · Level 200 Computer Engineering · Individual practical · 1 hour 30 minutes (1h15 to build, last 15 min to submit)
1. This is an individual exam
- Every student works alone and submits their own app. There is no group submission and no group mark. You are marked only on the code you submit yourself.
- You have been placed in Group 1, 2 or 3. A group is only a sitting batch: it decides which app you build and when you sit (see the schedule). It does not mean you work together.
- Everyone in the same batch gets the same brief, but each person builds their own Flutter project on their own laptop. Do not share code, files or screens with anyone.
2. Signing in
- Sign in with your student ID and date of birth (as on your admission records).
- The portal only opens during the scheduled exam window. Outside that window you cannot sign in or submit.
3. Building the app
- Create your own new Flutter project on your laptop (
flutter create). Build everything the brief asks for, by yourself. Test it in an emulator or on a device as you go. - Use only the Flutter SDK. No extra pub packages are needed.
- Write your name, student ID and group number in a comment at the very top of
lib/main.dart.
4. Submitting
- You submit for yourself. Sign in with your own ID and paste the full contents of your
lib/main.dart(andpubspec.yamlif you changed it). Nobody can submit on your behalf, and a classmate's submission earns you nothing. - Each student has two submission attempts. Your mark is the best of your own two attempts.
- Timing: 1 hour 15 minutes to build, then the last 15 minutes to submit. Use your first attempt around the 60-minute mark as a safety copy and the second when the app is finished — do not leave both attempts to the final minutes.
- If you run out of attempts, ask the lecturer — attempts can be added for individual students.
5. Marking
- Every submission is marked in real time against the published rubric (100 marks). You will see a provisional score and feedback within about a minute of submitting, and an SMS confirmation is sent to the phone number on record.
- The lecturer reviews all provisional scores before results are released. The lecturer's mark is final.
6. Academic honesty
- Code must be written by you alone during the exam. Identical or near-identical submissions between students will be investigated under the university's examination regulations.
- Do not share your code, and do not share your sign-in details. Submitting someone else's work — or letting someone submit yours — is an examination offence.
Batch schedule
| Group 1 Fri 04 Sep, 08:30 – 10:00 |
closed |
| Group 2 Fri 04 Sep, 10:00 – 11:30 |
closed |
| Group 3 Fri 04 Sep, 11:30 – 13:00 |
closed |
Each batch has 1 h 30 min: 1 h 15 min to build, the last 15 min to submit. Sign in only during your own group's slot, and submit your own work.
Go to sign inMarking rubric (100)
| Project structure & compilation | 10 |
| UI layout & widgets | 15 |
| State management | 15 |
| Forms & validation | 15 |
| Lists & dynamic data | 15 |
| Navigation & data passing | 15 |
| Code quality & Dart conventions | 10 |
| Header comment & completeness | 5 |