Back to Assessments
Year 10 Digital Technologies

Task 2: Minor A2 - About Me Swift Playgrounds Challenge (Student Package)

Task 2: Minor A2 - About Me Swift Playgrounds Challenge (Student Package)

Assessment details

  • Subject: Year 10 Digital Technologies
  • Assessment type: Swift Playgrounds practical project
  • Weighting: 15%
  • Raw mark total: 50 marks
  • Timing: Term 2, Weeks 4-6
  • Final checkpoint: Term 2 Week 6
  • Major project connection: This task builds the SwiftUI skills needed for the Simpsons House iOS app.

Purpose

This task assesses your ability to create, customise, test and explain a working Swift Playgrounds app. You will demonstrate SwiftUI layout, modifiers, interaction, debugging and reflection.

Pathway choice

Choose one pathway. Your teacher must confirm your pathway before final submission.

Pathway Who should use it Requirement
Standard pathway Students who have not submitted About Me before Build an About Me Swift Playgrounds app that introduces you through clear content, layout and interaction.
2025 alternative pathway Students who submitted an About Me task in 2025 Complete an approved Swift Playgrounds App Gallery challenge and customise it beyond the starter version.

Required submission components

Submit one organised evidence package that includes:

  1. Working Swift Playgrounds app
    • app opens and runs
    • required sections/screens are present
    • interaction works reliably
  2. App screenshots
    • screenshot of main screen
    • screenshot of at least one other section/screen
    • screenshot showing the interaction or changed state
  3. Code evidence
    • screenshot or copied snippet of key SwiftUI layout code
    • screenshot or copied snippet of interaction/state code
    • short annotation explaining what the code does
  4. Testing and debugging log
    • at least 4 tests with expected and actual results
    • at least 1 improvement made after testing or feedback
  5. Reflection
    • what you designed
    • what SwiftUI skills you used
    • what problem you fixed
    • how this prepares you for Simpsons House

Minimum technical requirements

Your app must include:

  • at least two clearly organised sections or screens
  • at least one meaningful interactive feature
  • intentional SwiftUI layout using views such as VStack, HStack, ZStack, ScrollView, TabView or equivalent
  • clear modifiers for fonts, colours, padding, backgrounds, images or shapes
  • readable personal content or approved App Gallery challenge content
  • evidence of testing and debugging

Suggested About Me features

  • Profile hero section with name, image/icon and short introduction.
  • Interest cards for hobbies, subjects, sport, music, games or goals.
  • A button that reveals a fun fact or changes the theme.
  • A favourites section using a list, grid or cards.
  • A personal design theme with intentional colours, icons, typography and spacing.

App Gallery alternative requirements

If you completed About Me in 2025, your App Gallery challenge must:

  • be approved by your teacher before you begin
  • be customised beyond the starter version
  • include evidence of your own code changes
  • include the same screenshots, testing log and reflection as the standard pathway
  • explain what the challenge taught you that will help with Simpsons House

Checkpoints

Checkpoint Evidence required Teacher authentication focus
Checkpoint 1: Pathway selected About Me plan or approved App Gallery challenge confirms appropriate task pathway
Checkpoint 2: App structure draft screens/sections and key SwiftUI layout confirms work is being built by the student
Checkpoint 3: Interaction button/toggle/picker/reveal/theme or equivalent confirms meaningful program behaviour
Checkpoint 4: Testing expected vs actual results and fixes confirms validation and debugging
Checkpoint 5: Final package app evidence, code evidence, screenshots, reflection confirms final submission is complete

Testing log template

Test number What I tested Expected result Actual result Change made
1
2
3
4

Academic integrity

Your app must be your own work. You may use teacher examples, Apple Swift Playgrounds examples and class notes, but you must customise the work and explain your own code decisions. Do not submit another student's app or a starter template without meaningful modification.

Command terms

  • Create: build a working app or feature.
  • Modify: change starter code or existing code for a purpose.
  • Debug: find and fix a problem in code or layout.
  • Validate: test expected vs actual behaviour.
  • Reflect: explain what you learned using specific evidence.

Curriculum links

  • DI10-2 (WA10DIGDI2): Design and prototype UX/UI based on client or user needs.
  • DI10-4 (WA10DIGDI4): Validate programs by comparing output against test cases.
  • DI10-5 (WA10DIGDI5): Implement, modify and debug programs in a general-purpose programming language.
  • DSN10-1 (WA10DIGDTDE1): Design alternatives considering functionality, accessibility, usability and aesthetics.
  • PM10-1 (WA10DIGDTPM1): Manage project work using an organised process.

Marking summary

Criterion Marks
App functionality and completion 10
SwiftUI layout and code quality 10
Interface design and personalisation 10
Interaction, testing and debugging 10
Documentation and reflection 10
Total 50

Grade guidance

Raw mark out of 50 Percentage Indicative grade
37.5-50 75.00-100.00% A
32.5-37 65.00-74.99% B
25-32 50.00-64.99% C
17.5-24.5 35.00-49.99% D
0.5-17 0.01-34.99% E
0 0.00% NA

Weighted mark conversion

This minor assessment is worth 15% of the course mark.

Raw mark Weighted mark
50 15.0
45 13.5
40 12.0
35 10.5
30 9.0
25 7.5
20 6.0
15 4.5
10 3.0
5 1.5
0 0.0

Submission checklist

  • My pathway was confirmed by my teacher.
  • My app opens and runs in Swift Playgrounds.
  • I included the required sections/screens.
  • I included at least one meaningful interaction.
  • I included final app screenshots.
  • I included key SwiftUI code evidence.
  • I completed a testing/debugging log.
  • I wrote a reflection using evidence from my app.
  • I acknowledged any external assets, examples or starter code.