Activity
Mon
Wed
Fri
Sun
Sep
Oct
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
What is this?
Less
More
The RoboNuggets Network (free)

68.6k members • Free

Mini Apps Competition

276 members • Free

75 contributions to Mini Apps Competition
Retiring NimConnect
I wanted to give the community a straightforward update: I’ve decided to discontinue NimConnect. I received detailed feedback from the Cycle 1 judges, and there was a lot in it that I agree with. The onboarding needed work, error handling wasn’t good enough, and the app tried to do too many things at once instead of making identity and contacts the clear focus. The biggest point for me, though, was about reach: NimConnect only really creates value for people who already have a Nimiq address. For something built around identity and human-readable handles, that feels like a fundamental limitation. Ideally, it should help bring new people into the ecosystem, rather than only becoming useful once they’re already there. I could narrow NimConnect down to identity + contacts, improve the onboarding and fix the UX issues — and I think that would make it a much better product. But it wouldn't solve that underlying limitation. So rather than continuing to polish it, I’ve decided to stop development and retire NimConnect. I’ve also decided not to participate in the next competition cycle. That decision is separate from the NimConnect feedback. I appreciate the judges taking the time to give detailed feedback, and I’ll take those lessons with me into future projects. My concern is with the transparency of the competition itself. I think things like how projects are evaluated, how scoring works, and how the final results are determined should have been clear and transparent from the start — not something that needed to be addressed afterwards. For me, that wasn't handled the right way in Cycle 1, and because of that I don't feel comfortable participating in the next cycle. Thanks to everyone who tried NimConnect, claimed a handle, gave feedback, or joined the Sip & Ship calls. I learned a lot from building it, even if this is where the project ends.
0
0
OpenScore — transparent competition judging
If you've ever run, judged, or entered a hackathon or competition, you've probably seen the same problems: scoring lives in spreadsheets, judges can influence each other, results get finalized with little context, and participants often get no useful feedback on where they actually stood. I built OpenScore to fix that. OpenScore is a self-hosted platform for running judged competitions end to end: define a detailed rubric, import submissions from GitHub, assign judges, score independently, generate useful feedback, publish leaderboards and result breakdowns, and keep a full audit trail of how the final outcome was reached. What makes it different: - Independent judging — judges don't see each other's scores while evaluating. - Detailed rubric scoring — score individual sub-metrics, not just broad categories. - Useful feedback — comments, quick tags, and optional generated summaries. - Locked means locked — changes after finalization require a reason and are audited. - Configurable transparency — choose exactly what participants and the public can see. - GitHub snapshots — lock judging to the exact commit that was reviewed. - Verifiable results — assessment sets can be Merkle-rooted and committed to Nimiq. - Full audit history — overrides, role changes, snapshot changes, corrections, and publishing actions are traceable. The goal is also to make competitions more useful for builders. If you didn't win, you should still be able to understand where you lost points, what judges valued, and whether improving the same idea for another round actually makes sense. 🔗 Live demo: https://openscore.nimiqminiapps.com/c/miniappscycle1 💻 Source: https://github.com/NimMiniApps/OpenScore Would love feedback from anyone who's run or participated in hackathons, grant rounds, bounty programs, or other judged competitions.
3 likes • 11h
I hope so as well transparancy is part of nimiq ethos right
0 likes • 3h
@Sam H finalzing vote is the judge need to sign a tx atleast
Would you add NimConnect support to your Mini App?
NimConnect lets users link a readable @handle to their Nimiq address, so apps can show and accept names instead of long wallet addresses. Would you be open to integrating it into your Mini App? If you choose maybe or no, I’d really appreciate hearing why in the comments. It would help me understand what is missing, whether the integration is too much work, or whether NimConnect simply does not add enough value for your use case. The integration uses the @nimconnect/profile-client package, and I’m happy to help or implement it for you if the project is open source. https://nimconnect.nimiqminiapps.com
Poll
12 members have voted
0 likes • 4d
@Dany Nimiqfr I might look into adding in protocol
1 like • 1d
@Dany Nimiqfr that’s good feedback thanks, I’ll see if I can make that happen
🏆 Huge congrats to the Nimiq Mini Apps Cycle 1 winners!
🥇 1st — Nimiq Space by Harley https://nimiqminiapps.com/apps/nimiq-space 🥈 2nd — NimJump by Emre Alt https://nimiqminiapps.com/apps/nimjump 🥉 3rd — NimQuest by mystiquemide https://nimiqminiapps.com/apps/nimquest Really impressive work from all three! 👏 I’ve featured the winners on the community-run Nimiq Mini Apps catalog, so they’re easy to find and try from the home board: 👉 https://nimiqminiapps.com You can read the official Cycle 1 winner announcement from Nimiq here: https://www.nimiq.com/blog/mini-apps-competition-cycle-1-winner-announcement Looking forward to seeing what everyone builds next!
🏆 MINI APPS COMPETITION: CYCLE #1 WINNERS!!
Cycle 1 is officially in the books. 62 Mini Apps submitted, all of them scored by the Nimiq Community Council, and the results are final. 🥁 Drumroll please… 🥇 1st place: Nimiq Space by @Harley NSpace An open multiplayer world where wallet-signed players can see who is online right now, paint a persistent 500x500 collaborative floor, and build rooms that sync live for everyone in them. 🥈 2nd place: NimJump by @Emre Alt An arcade game built around a minimal client-authority architecture, where the server replays every run itself instead of trusting the score the client reports. 🥉 3rd place: NimQuest by @mystiquemide A learn-and-prove Mini App with server-graded quizzes, where a completion only counts once you sign a one-time message in Nimiq Pay. Congratulations to all three. Winners will be contacted directly to arrange payout. To everyone else who submitted, thank you. You shipped something real in four weeks and set the bar high for future cycles. Every app you built is yours under the MIT License, so keep going with it. 🗓️ Cycle 2 opens August 24. Same $17,000 USDT prize pool, four Sip & Ship calls, submissions close September 18 at 23:59 UTC. If your app did not place this time, you can refine it and submit it again. Full breakdown on all three winners: https://www.nimiq.com/blog/mini-apps-competition-cycle-1-winner-announcement
🏆 MINI APPS COMPETITION: CYCLE #1 WINNERS!!
1 like • 3d
@Mini Apps Competition Thanks for the response. I’m not questioning the effort of the judges or the work of the winners, and congratulations to them. My issue is that I don’t think it’s fair to say “move on to Cycle 2” while builders are still completely in the dark about how their Cycle 1 submission actually performed. I submitted one app. Without scores or feedback, I have no idea whether the idea itself was competitive, whether it fell short on UX, functionality, usefulness/originality, or marketing, or whether it was actually close. That matters a lot when deciding what to do next. Should I improve and resubmit the same app? Was the concept never realistically going to score well? Should I spend weeks building something completely different? Or is it maybe not worth continuing at all if there’s no way to understand what the judges actually valued? The rubric tells us what can be scored, but without knowing how our submission was scored, we can’t learn anything concrete from Cycle 1. And to me, transparency is one of the main reasons to have a scoring system in the first place. If the scores are never shared, builders can’t verify where they stood, understand what to improve, or make an informed decision about whether to invest more time in the next cycle. Going into Cycle 2 completely blind could mean spending a massive amount of time improving and resubmitting something that the judges fundamentally don’t see as competitive. I’m not asking to challenge the winners or debate every judge’s decision. Even just the four category scores for my own submission would already give me something meaningful to work with. If the goal is to encourage builders to keep improving and participating, some level of scoring transparency or feedback feels essential.
0 likes • 3d
One extra point that makes this more important for me: builders are also being asked to release their submissions under the MIT license. So participating isn't just spending a few evenings trying something. It can mean investing a significant amount of development time and then releasing that work under a very permissive license that allows others to reuse it, including commercially. I'm fine with open source, but that makes it even more important to be able to judge whether participating again is actually worth that investment. Right now the choice for Cycle 2 is basically: spend another large amount of time building or improving something, release it under MIT again, and do that without knowing whether my Cycle 1 submission was close, far off, or whether the concept simply wasn't considered competitive. That's why even basic category scores would make such a big difference. I'm not asking for confidential judge discussions or trying to dispute the winners. I just want enough information to make an informed decision about whether investing that time into another competition cycle makes sense.
1-10 of 75
Chuck Veenvliet
5
309 points to level up
@chuck-veenvliet-3583
Builder

Online now
Joined Jun 5, 2026
Powered by