Show HN: Jynx, a matchmaking app to find gaming teammates(jynx.app)
jynx.app
Show HN: Jynx, a matchmaking app to find gaming teammates
https://jynx.app/
4 comments
Great project.
| Good:
* Confirmation email didn't land in spam
* Easy setup
* Lightweight app, quick install
| Improvements:
* Add a large default gallery of profile portraits matching the app's style (manga characters)
* Improve onboarding navigation consistency; avoid flows that go right, then left
* Older users like me may not be familiar with Tinder-style swipe actions; a quick tutorial/modal would help
* Ensure every game has a logo image
* Default username should not be derived from the email address
It means a lot you took the time to test it.
I thought about implementing a quick tutorial whenever users land for the first time on a feature, that's definitely coming soon.
Thank you for the feedback, I'll get around to it
smy_smy(1)
Live on App Store and Play Store: https://play.google.com/store/apps/details?id=app.jynx https://apps.apple.com/fr/app/jynx-where-gaming-gets-social/...
---
Hi HN, long time lurker, first time poster, be gentle.
Developer by day, vibe coder by night: Jynx is the project I used to ease into agentic engineering.
AI talks are mitigated, at best. But I'll talk about my experience here. Forgive my erratic style, it is what it is.
Working with Claude from the very beginning, it's been a blast. I had the "chance" to have the time necessary to learn and use AI a lot. Lots of different techniques that quickly became completely obsolete today.
Without LLMs, it would have been extremely hard to have the same app than I have today. I used Flutter (Dart) to avoid having to dev and maintain two codebases. It is not a language I knew. Learning the language first would have severely hindered the process.
For me, from copy/paste to using MCP then Roo Code, then Claude Code was an ecstatic process. I always loved having ideas but the time it would take me to build the thing and test it always felt too long. Not anymore.
So we carefully designed, iterated and implemented the two codebases for Jynx. One for the flutter app, one for the firebase backend. I chose Firebase to avoid having to maintain a server and be able to focus on the UI/UX of the app.
We started thinking about it in December 2024 and started devs early 2025; not working on it full time at all. We really poured our heart into it and we truly tried to make it as secure as possible. Even though we mean business, it is a passion project. By using the excuse of learning agentic flows, I took the time to inspect each aspects of the app's systems thoroughly.
Tech stack: - Flutter 3.41 / Dart 3.11 (single codebase, iOS + Android) - Firebase (Firestore, Cloud Functions in TypeScript, Auth, Storage, FCM) - Riverpod 3.1 + Freezed + json_serializable for state management & immutable models - Drift for encrypted local SQLite caching (offline-first architecture to optimize Firebase costs) - Clean Architecture with feature modules and mixin-based repositories - Sentry + Firebase Crashlytics for production error reporting - Freerasp for runtime app self-protection (tamper detection, root/jailbreak)
Agentic engineering artifacts: - Claude Code (Claude + GLM) as primary coding agent - 22 hooks, 18 skills, 13 instincts, 8 rule files, custom subagents, slash commands, MCP servers and plugins (instincts system from Affaan's https://github.com/affaan-m/everything-claude-code) - GitNexus - MemPalace for persistent context across sessions
Stats: 1,239 Dart files, 214k lines of code (excluding generated boilerplate), 30k lines of comments across the Flutter codebase.
I made a detailed cheatsheet document about my whole setup if you want it. I could post it or you DM me.
If you have questions, ask away, I'll gladly answer.
Test it and tell me what you think of it honestly, I won't get offended!
Take care, Antoine