OOP Todo App
A command-line todo app using classes, inheritance and file storage. First taste of software design.
Thirteen is the turning point. Old enough for OOP, Git and deployed apps; young enough that a board exam is not yet eating the calendar. One hour live, 1:1 or small group.
At 13, the best courses use the same tools professional developers use — Python with OOP, React, Git, real databases. These are the tracks our 13-year-olds thrive in.
Python, web and AI taster projects — a strong first step if your teen is undecided.
View course →
Zero to confident — functions, OOP, files, real mini-apps. The backbone of every other track.
View course →
HTML, CSS, JavaScript, Node, databases — ship a real deployed web app.
View course →
Pixel-perfect responsive UI, animations, Tailwind — portfolio-ready layouts and components.
View course →
Flutter + Firebase — build and publish real mobile apps. Teens love seeing their app on a phone.
View course →
Pandas, sklearn, neural nets — real AI projects with datasets, not toys.
View course →
Unity / Godot — full playable games with physics, characters and level design.
View course →
OOP in depth with BlueJ-friendly style — strong for ICSE/CBSE CS and Android foundations.
View course →If your teen already knows Python basics and has touched HTML/CSS, skip ahead into React, AI & ML, DSA or App Development. Free demo has a proper level check.
Looking for more? Browse the full courses catalogue →
A 13 year old who likes coding will start a personal project without being asked, join Discords, watch YouTube tutorials, try to deploy things. The job of a good teacher is to feed that fire without overwhelming it.
At 13, most of our students bring project ideas to class. A weather app, a personal blog, a Discord bot. We teach the skills around their idea rather than a syllabus.
Thirteen is the right age to open a GitHub account. Real commits, real pull requests. We guide first steps so the profile looks genuine by age 16.
Schools abroad and selective Indian colleges look for signals by Class 10–12. Starting a public portfolio at 13 gives 3–4 years of real projects by then.
These are the projects every 13 year old in our full-stack track completes. Real enough to show a future university, small enough to actually finish.
A command-line todo app using classes, inheritance and file storage. First taste of software design.
React component-based portfolio site, deployed to Vercel with a real custom domain.
A daily-journal mobile app with local storage. Runs on their own phone via debug APK.
Simple sklearn model that classifies tweet-style text as positive or negative. First supervised ML.
First repo, README, commits, branches, a merged pull request. Real source-control habits built at 13.
A full platformer in Pygame — characters, levels, score, sound. Published to itch.io.
Thirteen is the age where the curriculum stops being linear. The stages below are the common path, but we branch based on what the student wants to build.
We move past scripts into software. Classes, inheritance, try/except, imports. The first proper Python program structure.
Responsive layouts, DOM, a first React component. By the end they can spin up a React app and push to GitHub.
They pick: Flutter app track, or sklearn AI track. Real work begins. Weekly progress. First deployed piece of software.
GitHub polished, a readable portfolio site, and a gentle introduction to arrays and linked lists — getting ready for competitive territory later.
Same curriculum. Same teachers. Same recordings. The difference is whether your child learns best with one teacher's full attention, or alongside 4 to 6 classmates at their level.
One teacher, one learner, the full 1 hour. The teacher adapts pace in real time — slowing down on tricky concepts, speeding up where your child is already fluent. Best for focused learners, specific exam prep, or fastest progress.
4 to 6 students at a similar level, one teacher, 1 hour per session. Learners move faster when they see peers solve problems in different ways. Supportive, never pressured. Best if your child enjoys learning with others.
Thirteen is a clear step up. This table shows where and why.
| What to expect | Age 12 | Age 13 (this page) | Age 14 |
|---|---|---|---|
| Main stack | Python + JS + App starter | Python OOP + React + Flutter | Full stack + AI + DSA |
| Project scope | 3–5 sessions | Multi-week projects | Month-long projects |
| GitHub | First repo | Active portfolio | Contributions to others |
| AI depth | sklearn basics | Supervised ML | Neural nets intro |
| School link | Class 7 ICT | Class 8 CS prep | Class 9 board CS |
| Independence | Drives some | Drives most | Fully independent |
Recent reviews from families with 13-year-old teens in our programmes.
My son shifted from another platform where it was very video-heavy. Here the teacher actually watches him code and corrects as he types. In 3 months he built a React portfolio and a Python project. He calls the teacher on WhatsApp when stuck.
What I like: the class is 5 teens, not 50. They show each other's work at the end. My daughter built a journal app in Flutter. She put it on my phone. That is an engineer.
We have been with Modern Age Coders since our son was 11. At 13, he now commits to GitHub weekly. The teacher was very clear that OOP was the next step and paced it well.
Short, plain answers. If your question isn't here, tap the callback button at the top and a human will get back to you the same day.
Fill the form. Our counsellor calls you within 3 hours, understands your child's pace, and schedules a real demo with a real teacher. No card, no commitment.