Hey dev.to 👋
I’m a solo developer currently building Fronex.fun, a Telegram-native social prediction gaming Mini App on TON.
The idea is simple:
Prediction experiences should not feel like complex trading dashboards.
They should feel closer to a group chat, a tournament, or a community game — something people can open inside Telegram, understand quickly, and share with friends.
What is Fronex.fun?
Fronex.fun is a Telegram Mini App for social prediction gaming.
The first major launch focus is WC2026, with prediction games, tournaments, leaderboards, and community-powered markets.
The goal is not to build another desktop-first prediction platform.
The goal is to build something that feels native to Telegram communities.
Why Telegram?
Telegram already has the communities.
Football groups, crypto groups, regional communities, TON builders, meme communities, and private groups all live there already.
So instead of asking users to download a new app or learn a new social graph, Fronex starts where the conversations already happen.
Inside Telegram.
Why TON?
TON makes sense because it is deeply connected to the Telegram ecosystem.
For Fronex, the technical direction is:
- Telegram Mini App for the user experience
- TON for wallet and settlement flows
- off-chain infrastructure for fast product interactions
- community-created markets through Market Owners
- tournaments and leaderboards for social engagement
The challenge is making the experience feel simple on the front end while keeping the infrastructure serious underneath.
What I’m building first
The first version focuses on the core product:
- Telegram Mini App flow
- user onboarding
- prediction market interface
- tournament / bracket experience
- leaderboard
- Market Owner flow
- wallet and transaction testing
- basic admin and moderation tools I’m trying to keep the launch version focused. Not everything needs to exist on day one. The important thing is that the core loop works. Open Telegram → join Fronex → make a prediction → follow the result → share with the community.
Why I’m writing here
I’m going to use dev.to to document the real build process.
Not just polished announcements.
I want to write about:
- Telegram Mini App development
- TON integration
- Web3 product architecture
- AI tools for launch marketing
- building in public
- product decisions
- what breaks
- what gets cut
- what I learn while shipping
I think the messy parts are usually more useful than the perfect parts.
What’s next
My goal is to keep posting updates as Fronex moves from build sprint to launch.
Some posts will be technical.
Some will be about product strategy.
Some will just be honest notes from building something under a real deadline.
If you’re building with Telegram, TON, Web3, AI tools, or community products, I’d love to connect.
Thanks for reading.
Predict the next frontier.
Top comments (0)