If you missed the last post, I launched WishArena on WishIT last week.
Short version: I had a late-night idea, tweeted it, and 40 hours later the thing was live inside WishIT. Fan wall, flag picker for all 48 World Cup nations, and a template — the whole thing. No sign-up required to participate.
If you want the full gist of how that happened, read it here first:
Read Also: I Tweeted an Idea at 10 pm. It Was Live 40 Hours Later →
This post is about what happened after.
Users came. And it didn't go as I expected.
Omo. I thought people would just drop predictions and move on.
Instead, they stress-tested the whole WishIT platform like mad. 😭
Navigation gaps I had been living with for months — someone found them and told me. Mobile UX that wasn't fully ready — people slapped it on me. One person even asked if they could install WishIT on their phone like a proper app.
That last one sha. When a user asks for a mobile app, they aren't complaining — they are telling you the product is valuable enough to live on their home screen. Na signal. Big one.
I treated everything as direction, not complaints. And within days, serious changes had shipped.
What was actually shipped
This is the part where a great part of me is proud of.
All of this came directly from what users were doing and saying on WishArena and WishIT as a whole:
- PWA support — you can now install WishIT on your phone. Service worker, offline page, app icons, the whole thing.
- Mobile-first redesign — the entire navigation rebuilt around how people were actually using it
- Custom Icons - the first phase of our custom icons started rolling out, like our WishArena icon, Templates Icon, WishDrop icon and more coming in more updates.
- Global bottom navigation — logged-in experience now feels like a proper social app
- Unified layouts — Arenas, Templates, and Dashboard now look and feel like one coherent product
- Arena follow — you fit follow an Arena and get notified when things happen
- Push notifications — yes, actual push. Built the whole infrastructure for it.
- Match events system — granular tracking of what happens inside matches
- Live match tracking — public match data, real-time updates
- Voting systems — for teams and nominees, clean and fast
- Account management improvements — soft delete, account restore, data export — proper GDPR-level stuff
- Content pages moved to database — admin can now manage content directly without touching code
- Cron jobs — automated background tasks now running properly
- Security and performance improvements across the board I bin dey think say na small sprint. E turn into a whole transformation. 😅
The thing that actually had me
After all of this, I sat down and thought about something.
All these improvements — they came from users. Real people wey showed up, participated, and cared enough to tell me what went wrong with their various experiences.
But how many people found issues and just left? How many edge cases never surfaced because the right person never encountered them?
I caught the ones who happened to speak up. The rest? I don't know.
And that is a problem. You can't build a solid product by just waiting for the right user to find the right bug at the right time and then decide to tell you about it.
You need structured testing. People who would go into your product specifically to find problems — not people who just happened to stumble into one.
Enter Twnhall
That realisation is what brought Twnhall back to my mind.
Twnhall is a developer-to-developer testing platform. The concept is clean — you submit your product, define what you want people to test, and other developers go through it properly and give you real feedback. In return, you test their own products too. Everybody benefits.
Ship better. Test each other. That is literally their tagline, and it makes total sense.
This is not a partnership announcement in the corporate sense. It is something that makes sense for where NFORSHIFU234 Dev is right now — a studio that is building real products for real users and needs a reliable way to catch problems before they reach production.
The plan is:
- Submit WishIT and future products to Twnhall for structured testing
- Have an official partnership where we can give Twnhall users early access to beta features on WishIT, and give WishIT users who are developers can also join Twnhall and contribute to testing other products
- Participate actively — not just submit and receive, but test other builders' work too.
E go benefit both sides. Twnhall gets active projects and real contributors. NFORSHIFU234 Dev gets structured feedback before things go live.
Read Also: Why NFORSHIFU234 Dev Is Making Community Testing a Core Part of How We Build → The studio-side breakdown of this same decision — more technical, more detail on what community testing looks like going forward.
The lesson sha
WishArena was supposed to be an engagement experiment.
It turned into a product audit, a stress test, and honestly — a wake-up call about how I want to build going forward.
Community feedback improved WishIT. That much has already happened.
Community testing is going to improve what is coming next. That is the new goal.
Anyhow sha. E go be. 🏟️
— Shifu Building WishIT under NFORSHIFU LOGICFORGE LTD, somewhere in Nigeria.
Try WishIT: wish-it.app Try Twnhall: twnhall.com Follow the build: @iamnotshifu