You have six email accounts. You know you do. The work one, the personal one, the one you made for newsletters, the one your bank forces you to use, the one from that freelance gig three years ago, and the burner you used to sign up for that free trial you never cancelled.
And every single time a login screen demands an OTP, you become a juggler with no hands — flipping between inboxes, searching for the latest code, praying it hasn’t expired in the 12 seconds it took you to find it.
Now imagine doing that while screen-sharing with a client. On a Zoom call. With the clock ticking down on a verification code that gives you 60 seconds and zero mercy.
The most painful problems aren’t the exotic ones. They’re the ones so mundane that nobody in a position of power bothers to feel the pain.
Enter Jenin. Fourteen years old. Toronto, Canada. Six email accounts, just like you. And instead of complaining about it on Twitter like the rest of us, he built OpenOTP — a native Swift tool that does the one thing every email client should have done years ago: surface your OTPs without the circus.
His first real open source project. Built for himself, because he needed it. Posted on Hacker News with the kind of earnest introduction that makes cynical tech veterans do a double-take: “Hey! I’m Jenin, a 14 year old in Toronto, Canada!”
And here’s where the story gets good.
The top comment wasn’t from another teen. It wasn’t from a hobbyist tinkering on a Sunday. It was from someone who runs an agency — multiple clients, multiple emails, multiple moments of quiet panic while sharing a screen and fumbling for the right OTP.
“This is godsend for me,” they wrote.
Read that again. A professional, someone whose livelihood depends on smooth client interactions, is calling a teenager’s weekend project a godsend. Not the latest update from Google. Not a feature in Outlook. Not some enterprise SSO solution that costs $40 per seat per month.
A kid’s app.
The market doesn’t care about your pedigree. It cares whether your software stops the bleeding.
Let’s talk about why this matters beyond one clever app.
Every major email client — Gmail, Outlook, Apple Mail — has had years and billions of dollars to solve this. They haven’t. Not because it’s technically hard. It’s trivially easy to detect an OTP in an email and surface it. But it’s not on a roadmap. It’s not in a sprint. It’s not someone’s OKR. Because the person who feels this pain is you, and the person who sets the roadmap is sitting in a conference room wondering why engagement metrics on their AI summary feature are flat.
This is the gap. This is always the gap. The people closest to the problem are rarely the people holding the budget.
And that’s what makes what Jenin did — and what programs like Hack Club Horizons do — so quietly radical. They don’t wait for permission. They don’t file a feature request and pray. They build. They ship. They put it out into the world and let the market decide.
The best software doesn’t come from a roadmap. It comes from a bruise.
Hack Club Horizons is flying teenagers to seven countries for hackathons. That’s not a coding boot camp. That’s not a resume-padding exercise. It’s a bet — a bet that if you give young people real problems, real tools, and real community, they’ll produce things that embarrass the incumbents.
OpenOTP is not going to disrupt Google. It’s not going to raise a Series A. It’s a small, native, open source tool built by someone who can’t legally drive yet. And it solved a real problem for a real professional within hours of being posted.
That’s the whole point.
We’ve built an industry that worships scale and dismisses smallness. We’ve convinced ourselves that “real” software comes from teams of fifty, with design systems and sprint ceremonies and a Notion workspace that has more words than the product. Meanwhile, a 14-year-old in Toronto shipped something useful in the time it takes most companies to schedule the kickoff meeting.
Stop waiting for the giants to fix what a kid can solve on a Saturday. The tools are here. The problems are yours. The only thing missing is the audacity to start.
So go check out OpenOTP. Star the repo. Tell Jenin what you think. And the next time you’re fumbling through six inboxes for a verification code that’s already expired, remember: someone tried to save you from this. They just happened to be fourteen.
FAQ
Q: Isn't this just a tiny app that doesn't scale?
A: That's exactly the point. It doesn't need to scale. It needs to work for the person using it. A professional agency owner called it a godsend within hours of launch. Scale is a business concern, not a user concern.
Q: Why haven't big email clients solved this already?
A: Because the people setting roadmaps don't feel the pain. OTP retrieval is a user problem, not a metrics problem. It won't move the needle on engagement dashboards, so it never makes the sprint. That's the gap indie developers fill.
Q: Does this actually prove anything about young developers?
A: It proves that proximity to a problem matters more than pedigree. Jenin built this because he has six email accounts and felt the friction daily. Most enterprise software is built by people who have never been the user. That's why it's often so painfully out of touch.