The Super-App Trap: Why doing everything usually means doing nothing
Building a one-stop-shop for student success sounds great on a slide deck, but how do you actually ship code that doesn't feel like a cluttered mess?

I’ve seen this movie before. Someone looks at the messy, broken reality of youth unemployment and decides the fix is a "Super-App" that handles everything from finding a hostel in Owerri to landing a junior dev role in Lagos.
Ukiyo, a South African outfit, just launched their "Global Student Support Platform." They want to be the one-stop-shop for scholarships, jobs, mental health, and housing. It’s an ambitious play, but as a dev who’s wrestled with feature creep, I’m sweating just thinking about their product roadmap.
The "Everything" Problem
When I build, I obsess over the user’s primary intent. If a user comes to my app to solve a problem, and I force them to navigate a sidebar full of "wellness services" and "accommodation deals" when they just want to see if they’re qualified for an internship, I’ve already lost them.
The Ukiyo team is trying to bundle the entire student journey. That sounds nice in a pitch deck, but technically? That’s a nightmare. You’re not building one app; you’re building five different products that need to share a database. If the job board is clunky, the user is going to assume the housing section is just as broken, and then they’re gone.
Where the Rubber Meets the Road
We have a massive problem with "sapa" and joblessness here in Nigeria, and I know guys in Yaba and even down in Port Harcourt working on similar platforms. The temptation to build a "one-stop-shop" is strong because it feels like you’re doing more to help.
But look at the data. They have 4,200 users and a few thousand click-throughs. That’s a start, but it’s a drop in the ocean. The real test isn't having the features; it’s having the "intelligent matching" they’re promising.
Why I’m Skeptical of the "Full Cycle"
You don’t solve systemic unemployment by adding more tabs to an app. You solve it by getting the right candidate in front of the right recruiter, fast.
If I’m a student in a small town trying to find my first job, I don’t want to be "supported" through every milestone. I want a bridge. I want a direct line to a company that won’t ask me for five years of experience for an entry-level gig.
The risk here is that Ukiyo becomes a jack-of-all-trades and master of none. If I were the lead dev there, I’d be fighting every single day to stop the scope from leaking into "wellness services" until the core job-matching engine was so good it felt like magic.
Final Thoughts
I respect the grind. Nozuko Mzamo and her team are trying to fix a real, painful gap. But building software for the "full journey" is the fastest way to build a mediocre product. I’d rather see them ship one feature that actually gets someone hired, rather than a whole suite of tools that just keeps them browsing.
Let’s see if they can pivot from "we do everything" to "we do this one thing better than LinkedIn." That’s where the real impact is hidden.
Related from Nigeria
Let's build your next big product.
Accepting project-based freelance, remote engineering roles, and hybrid positions.