How a 16-Year-Old Competitive Swimmer Built a Real iOS App (and Why It Stands Out)

Kimaya, a 16-year-old competitive swimmer, wanted lap-by-lap feedback her coach could not always give, so she built SwiftLap: a native iOS and Apple Watch app in SwiftUI that logs laps from your wrist and reviews swims on your phone. She had no engineering background. The takeaway: a teenager can ship a real, verifiable product by prompting AI with coaching.

What did a 16-year-old actually build?

Kimaya (GitHub @KimayaVP) built SwiftLap, a swim-tracking app that runs natively on iPhone and Apple Watch. It is written in SwiftUI, Apple's modern framework for building real apps that feel at home on the platform.

The app does two concrete things:

• Logs laps directly from your wrist while you swim, using the Apple Watch.
• Lets you review those swims afterward on your phone.

This is not a slideshow, a worksheet, or a class project that lives in a folder. It is a working product with code anyone can open, read, and run. That distinction matters more than most people realize.

Why did she build it in the first place?

Kimaya is a competitive swimmer. She wanted detailed, lap-by-lap feedback on her swims, the kind that helps an athlete shave seconds and fix form. Her coach could not always provide that level of detail.

So instead of waiting for a tool to exist, she built the tool. The problem was personal and specific, which is exactly what makes the project credible. She was not building an app to have an app. She was solving something she felt every time she got in the pool.

That is the pattern behind almost every standout student project: a real itch, scratched by the person who has it.

How does someone with no engineering background ship a native app?

Here is the part that surprises people. Kimaya had no professional engineering background. She did not spend years grinding through computer science prerequisites before she was "allowed" to build something real.

She built SwiftLap by prompting AI, guided by coaching. That means she described what she wanted, worked through the AI's output, tested it, hit problems, and pushed through them with a mentor in her corner. The AI wrote a lot of the code. Kimaya made the decisions, understood the structure, and steered the whole thing to a finished product.

This is the method we teach at StepAhead. Students learn to build and ship real software by prompting AI, coached by AI plus mentor Sahil Modi. The goal is not to memorize syntax. The goal is to ship.

Why does a shipped, public project stand out to top universities?

Admissions officers and scholarship committees see thousands of applications that say a student is "passionate about technology." Almost none of them come with proof.

Kimaya's project comes with proof on two fronts:

• A live app that actually runs on real Apple hardware.
• A public GitHub repository anyone can inspect, line by line.

You cannot fake a working iOS app. You cannot fake a code history that shows real decisions and real debugging. That is what makes a project like this hard to ignore: it is verifiable. A reviewer can click the link, read the code, and see that a 16-year-old genuinely built something that works.

Universities that care about builders are looking for exactly this signal: a student who saw a gap in their own life and closed it with a real product, not a story about intending to.

What makes this a "real" project and not a tutorial clone?

There is a meaningful difference between following a tutorial and shipping a product. Tutorials hand you the destination. Real projects make you find it.

SwiftLap has the marks of a real project:

• It targets a specific, demanding platform combination: iPhone plus Apple Watch.
• It solves a problem the builder personally has, which forces real design choices about what to track and how to show it.
• It exists in public, at a verifiable address, with the builder's name attached.

When a student can point to something running on a device and say "I built this because I needed it," the conversation changes. They are no longer a candidate describing potential. They are a builder showing results.

Could a student reading this do the same thing?

Yes, and that is the entire point of telling Kimaya's story. She is not a prodigy who was coding since age six. She is a swimmer who wanted better feedback and decided to build it.

The repeatable formula looks like this:

1. Find a real problem in your own life, school, sport, or hobby.
2. Describe the smallest useful version of a tool that would solve it.
3. Build it by prompting AI, with coaching to keep you unstuck.
4. Ship it somewhere public, with code anyone can verify.

That last step, shipping, is the one most people skip. It is also the one that separates a hopeful applicant from a credible builder. A finished, public project does work for you long after you submit it.

StepAhead's entry product is a $100 bundle of 13 build projects designed to walk you through exactly this loop, from idea to shipped software, the same method Kimaya used to build SwiftLap.

Where do you start?

You start by building one real thing. Not a hundred. One.

If Kimaya's story sounds like the kind of standout project you want on your own record, start with StepAhead's $100 bundle of 13 build projects and ship your first real app by prompting AI with a mentor in your corner. The problem you solve can be as personal as a better way to track your laps. What matters is that you build it, ship it, and can prove it.