The Apple Swift Student Challenge: Or How Two Aussie Teenagers Ended Up Beating Half the Planet
Photo by 晓鸟 蓝 on Pexels.com
Every year, somewhere in the world, a student opens a laptop and thinks, Right. I’m going to build something important.
Most of the time, that thought dies somewhere between Netflix and procrastination.
But sometimes, very occasionally, it turns into something extraordinary.
Enter the Apple Swift Student Challenge. This is not a gentle university assignment. This is Apple leaning back in its very expensive chair and saying, Alright then. Impress us.
And if you do? They don’t hand you a sticker and a participation ribbon. They recognise just 350 winners globally. Fifty of those are flown to Cupertino for three days inside Apple Park, where the future is quietly assembled by people in very clean sneakers.
Which is how two 17-year-old twins from the Sunshine Coast ended up shaking hands with Apple engineers instead of revising for Year 12 exams.
What This Thing Actually Is
The Swift Student Challenge is Apple’s global competition for student developers. You build an app playground experience using Swift. It needs to demonstrate creativity, technical skill, and ideally, solve a real problem.
Apple is not interested in neon gradients or buttons that bounce for no reason. They want ideas. Brains. Intent.
Edward Mann found his idea while being bored out of his mind.
“The idea for my submission, Graphics Handbook, was built around my experience of learning Computer Graphics and how I thought I could make teaching it more accessible and enjoyable for others. I learnt Computer Graphics the traditional way, involving a lot of text-based explanations and code examples. While this is a perfectly valid way to learn programming, Computer Graphics is all about how computers make 2D and 3D images, so why not leverage that. This idea eventually led to a fun and interactive app designed to teach people, regardless of their coding ability, how Computer Graphics work in a very visual and hands-on way.”
Sensibly, Edward decided that learning graphics by looking at graphics might be a good idea. Radical, I know.
Oscar Mann’s idea came from something much heavier.
“My source of inspiration was one of my friends. They are diagnosed with anxiety disorder, and when they shared their experiences with me, I could see how much it was impacting their life. My app focuses on nail picking and chewing to indicate levels of anxiety, which I find for myself is a symptom of stress.”
Two very different ideas. Same outcome. Apple said yes.
The Bit Everyone Underestimates: Actually Building the Thing
This is where most people quietly give up.
Edward didn’t.
“I spent my entire summer school holidays working on my app, which amounted to hundreds of hours of learning, coding, writing, and testing. It was very content heavy, meaning I needed to write a lot of descriptions and explanations, and make the interactive diagrams and other fun elements that go along with it. Despite all the time I spent on it, I still had to submit the app with some of the more advanced content missing.”
Hundreds of hours. And still unfinished. Which is exactly how real software works.
Oscar’s experience was similarly relentless.
“I spent the most part of my summer break working on my project, so roughly eight weeks. It was certainly challenging to stay motivated and focused when approaching the end of the project, but my family helped a lot through encouragement and support. Overall it was a pretty big sacrifice, but ultimately I enjoyed pushing myself.”
This is the bit brochures never show you. No glamour. Just work.
The Technical Pain (And Why That Matters)
Edward decided to make life harder for himself by diving headfirst into Metal.
“The most technically challenging part of making Graphics Handbook was working with Apple’s graphics API, Metal, which is the key component that allows Apple computers to generate images onto a screen. I hadn’t worked with Metal before, but I did have some experience with similar APIs, such as OpenGL. Metal is a lot more technically advanced, so I had to relearn a lot of what I already knew. What I didn’t realise at the time was that, by challenging my own understanding of how Computer Graphics work, I now understood many concepts at a much deeper level, enabling me to work that new knowledge into the app.”
Oscar, meanwhile, decided to juggle multiple advanced frameworks at once.
“The aspect of my project that I found most challenging was the computer vision pipeline. I had to develop a system that could take a stream of video frames from the device’s camera and simultaneously detect the user’s hand position and outline. It meant using some pretty complex frameworks, like Vision, Combine, and Metal, all at once.”
This is not beginner coding. This is serious engineering.
Why Apple Actually Noticed Them
Edward believes personality mattered.
“I put a lot of work into making sure that my experience was unique, right from the moment someone first opens the app. One of these distinctive elements was the in-app assistant, Pix, who is always around to explain concepts more deeply. A key component to Pix was their dialog was written in a different, more friendly style to the rest of the app’s more informative style.”
And then there’s this, which Apple engineers love.
“Another such element was the custom backgrounds that were tailored to match each topic the user was exploring. I made these to show off the real world applications of what they were learning, and the actual code for each background could also be found in the app. All of these elements and more gave the app a personality, which I think was very valuable and a large part of what ultimately led to my entry standing out.”
Oscar’s approach was simpler.
“I think what made my entry stand out to the judges was my focus on the user experience. Every aspect of the app was designed to provide an intuitive and simple process for tracking anxiety. This is what my goal was, to make anxiety tracking more accessible.”
No nonsense. No showing off. Just usefulness.
The Bit Where Apple Changes Your Life
Edward was selected as a Distinguished Winner and flown to Cupertino.
“The three day trip to Cupertino was quite literally a once-in-a-lifetime experience. It was amazing to visit Apple Park, see the World Wide Developers Conference live, talk with Apple employees and attend special sessions run by Apple.”
But the real highlight?
“One of my favourite things was meeting the other 48 Distinguished Winners (one couldn’t make it) from all over the globe and hearing their stories. It was fun and really inspiring to meet so many other people with the same passion for coding but from different backgrounds and with different interests. I can confidently say I will never forget the experience and the friends I made there.”
Oscar didn’t go to Cupertino, but the win still mattered deeply.
“My app Nail Anxiety was my third entry to the Challenge, and my first win. Competing in the challenge each year certainly developed my coding and problem solving skills, but personally, each submissions meant something different to me. I found myself disappointed when my second entry to the competition in 2024 didn’t win, and I felt disheartened by that.”
And then came the shift.
“So for my third time round, I decided to forget about results and prizes, and just focus on making the best and most meaningful app I could.”
That, right there, is the lesson.
Was It Terrifying Putting It In Front of Apple?
Edward was honest.
“When it came time to submit the app, I was nervous but also thankful, as it was nice to have a definitive finish for such a long project.”
But Apple, it turns out, isn’t scary at all.
“At Apple Park in Cupertino, everyone was super friendly and approachable, which meant talking about and presenting my project to people, Apple or otherwise, was surprisingly easy.”
Oscar agrees, even without the US trip.
“I didn’t find it daunting to enter the Swift Student Challenge, because I knew that I was capable of winning if I worked hard.”
And on presenting:
“I think the environment that Apple creates (especially during the Swift Student Celebration in Sydney) is really encouraging and supporting of all people, no matter the experience or skill level.”
Should You Enter?
Edward’s advice is refreshingly grounded.
“The best advice I would give to any students thinking about entering is to be happy with the outcome, whether you win or not. I know it sounds cliche and a bit rich coming from me, but I would be just as proud of myself and my app even if I didn’t win. Whether you win or not doesn’t make it any less valuable.”
Oscar’s is sharper.
“I think the best advice I could give is to forget about the competition. The real benefit of the Swift Student Challenge is how you improve when working on your project. You grow as both a coder, but also a problem solver, which I thing is many times more important than winning.”
The Final Word
In 2026, everyone talks about building apps. About tech careers. About startups.
Very few people actually build anything.
The Swift Student Challenge forces you to stop talking and start shipping.
And sometimes, if you do it properly, Apple notices.
Applications close at the end of February.
Stop thinking about it.
Start building.
Zachary Skinner is the editor of TechDrivePlay.com, where tech, cars and adventure share the fast lane.
A former snowboarding pro and programmer, he brings both creative flair and technical know-how to his reviews. From high-performance cars to clever gadgets, he explores how innovation shapes the way we move, connect and live.
