M01Weeks 1-4
Thinking in screens
- Who is this for and what do they need in ten seconds
- Paper sketches and flows
- Interface basics: hierarchy, contrast, spacing
- Critique a real app honestly
All specialisations
Specialisation · 04/16
App Development
“The idea in your head, installed on someone else's phone.”
Levels
2
Middle · Senior
Outcomes
5
Skills children walk away with
Pathways
4
Future careers unlocked
Quick answer
App Development at NASCA is a hands-on, project-led specialisation for Middle, Senior. Students learn Design usable screens, Handle state and data, Test with real users and explore careers in App Developer, Frontend Engineer, Product Designer. The four-stage journey runs across a full academic year and is World STEM Federation accredited.
Grade 6–12: A working app on a real phone, used by real people in the school.
The idea
App development is where every other skill has to hold together at once: interface design, logic, data, testing and the patience to fix what users break. Students start with visual builders like MIT App Inventor, then move to modern web apps and cross-platform frameworks. They design screens on paper before writing code, run usability tests with classmates who are not developers, and release at least one app that other students in the school actually install and use. Feedback from real users, not a rubric alone, drives the second version.
The journey
A four-stage arc
01
Sketch
Draw the screens before writing a line of code.
02
Build
Turn the sketch into something that runs on a phone.
03
Test
Hand it to someone who has never seen it and watch silently.
04
Release
Fix what they broke and put version two in their hands.
Signature project
Flagship build
The App the School Uses
One student-built app adopted for a real school need, maintained by the next cohort after them.
Why it matters
An app is the first thing a child builds that a stranger can use. Design, logic, data and testing must all hold together at once, which is exactly why it teaches so much so fast.
A typical session
- 01Review yesterday's user feedback
- 02Sketch the screen on paper first
- 03Build the smallest version that runs
- 04Hand it to someone and watch silently
- 05List the three things to fix next
The curriculum
What they actually learn
Six modules across an academic year. Every module is hands-on, project-led and ends with something children have built and can show.
M02Weeks 5-10
First working app
- Build in MIT App Inventor
- Buttons, inputs and screens that talk to each other
- Store something and get it back
- Install it on a real phone
M03Weeks 11-16
The web as a platform
- HTML, CSS and JavaScript with purpose
- Layouts that survive a small screen
- State: what the app remembers and when
- Deploy to a live URL
M04Weeks 17-22
Data and accounts
- Save data to a cloud database
- Sign-in and what privacy actually requires
- Handle errors and empty states
- Never trust user input
M05Weeks 23-27
Testing with humans
- Run a usability test without helping
- Record what confused them
- Prioritise fixes by pain, not by preference
- Version two, built on evidence
M06Weeks 28-30
Release
- Icon, name, description and screenshots
- Publish or distribute inside the school
- Write the support notes
- Hand over to the next cohort
Showcase moments
Three highlights through the year
- Term 1
Phone in hand
Every child installs their own first app and shows a parent.
- Term 2
Usability day
Younger students test the apps while the builders sit on their hands.
- Term 3
Adoption
One app is chosen for a real school need and maintained beyond the year.
For parents
The most useful thing you can do is use the app badly and tell your child what confused you. That feedback is gold.
For teachers & schools
Design comes before code in every unit. The visual builder route means a non-programming teacher can run the first term comfortably.
What children build
- Utility apps
- Quiz and study apps
- School service apps
- Progressive web apps
- Published prototypes
Tools & tech
MIT App InventorFigmaHTML, CSS and JavaScriptReactFirebaseAndroid test devices
Levels offered
MiddleSenior
Outcomes
What they walk away with
01
Design usable screens
02
Handle state and data
03
Test with real users
04
Fix bugs under pressure
05
Release a version
Questions parents ask
FAQ
The honest answers to the questions families ask us most.
iOS or Android?
Android and progressive web apps, because they install without an approval queue or a developer fee. The skills transfer directly.
Does my child need a phone?
No. The lab has test devices, and everything also runs in a browser.
Will the app be published publicly?
Only with your consent. Most projects are distributed inside the school, which is where the real users are anyway.
What if my child cannot design?
Design is taught here as rules and testing, not as talent. Ugly and usable beats beautiful and confusing, and we say so.