Game planning & development
We plan and develop WebGL, Telegram and mobile games around your project goals. Agree the platform, multiplayer features, servers and operating responsibilities to define the builds and deliverables you need.
View package budgetsReleased web games
Ablecity handled planning, full development, and web launch for ODDSHOT and RUMBLEPOP. View the gameplay trailers and visit the live services to see the delivered games.
The video could not be loaded. Open the video file below or visit the game service.
If the video does not play, open the video file. Open the ODDSHOT video file
Gameplay trailer · 30 seconds
Real-time competitive multiplayer game
Registration and login are required to play.
The video could not be loaded. Open the video file below or visit the game service.
If the video does not play, open the video file. Open the RUMBLEPOP video file
Gameplay trailer · 30 seconds
Real-time competitive multiplayer game
Registration and login are required to play.
Development services
Browser
Evaluate core gameplay in a browser without an app installation.
Scope the WebGL build, basic server, ranking and admin tools.
Explore WebGL game developmentTelegram / Games
Review how players launch and share games in Telegram communities.
Scope the Bot, Mini App, ranking, sharing and reward structure.
Explore Telegram game developmentTelegram / Services
Build booking, ticketing, commerce and community flows.
Agree the payment, form, QR and notification features you need.
Explore Mini App developmentMobile
Evaluate gameplay and QA before a store release.
Scope the Unity/Unreal MVP, QA and store preparation.
Explore mobile game developmentOperations
Define the operating work needed after launch.
Agree events, balancing, bug fixes and server monitoring in the operations contract.
Discuss LiveOpsThese are possible project components. Features and deliverables vary by package. Confirm the actual scope in the estimate and contract.
Development packages
Timelines and budgets vary by genre, multiplayer requirements, Web3 integration, server operations and release platform.
On smaller screens, scroll the table horizontally to review inclusions and exclusions.
| Package | Timeline | Starting Budget | Included | Excluded |
|---|---|---|---|---|
| Game Concept Audit | 1-2 weeks | KRW 5M-10M | Genre/BM/policy/technical risk review | Development |
| WebGL Prototype | 4-6 weeks | KRW 25M-50M | Core loop, WebGL build | Advanced realtime multiplayer |
| Telegram Mini Game | 4-8 weeks | KRW 30M-80M | Bot, Mini App, ranking, sharing | Token legal review |
| Multiplayer MVP | 8-12 weeks | KRW 60M-150M | Realtime server, room, ranking, admin | Large-scale concurrency optimization |
| Mobile Game MVP | 12-20 weeks | KRW 120M-300M | Unity/Unreal, iOS/Android, QA | Marketing / UA |
| Web3/TON Integration | +2-8 weeks | KRW 20M-100M+ | TON Connect, wallet, reward design | Legal opinion |
| LiveOps Retainer | Monthly | KRW 3M-15M/mo | Server, bugs, events, balance, reports | 24/7 NOC |
Confirm separately whether original artwork and sound licences, store accounts, cloud costs, marketing, legal review and 24-hour monitoring are included.
Development process
Review the gameplay loop and technical and policy risks first. Test the core experience with a prototype, then proceed with the agreed MVP, QA and release preparation. Post-launch operations are defined in a separate contract and SLA.
3–5 days
Review requirements, genre, platform and risks to decide whether to proceed or hold.
1–2 weeks
Review the gameplay loop, business model, technical complexity and budget.
4–6 weeks
Use a playable build to test assumptions about enjoyment and repeat play.
8–12 weeks
Implement the agreed login, server, ranking, payment/reward and admin features.
2–4 weeks
Prepare QA, deployment, policy checks and monitoring criteria.
Monthly
Review events, balance, bugs and metric reports to decide whether to continue operations.
Each item is discussed for your project. Actual deliverables and operating support are confirmed in the estimate and contract.
Web3 and platform policies
Review TON Connect wallet integration and the reward structure.
Token and NFT features are implemented after reviewing country, platform and store policies.
Guaranteed-return or speculative models are excluded from the standard development scope or require a separate legal review.
Review App Store and Google Play review and payment policies before mobile development.
Address bots, abuse, fraudulent rewards and server costs in the initial design.
Release countries, payments, languages and time-zone coverage affect the estimate and schedule.
Estimate and contract terms
The handover scope is defined by the contract and completion of the final payment.
Cloud servers, external APIs and LLM usage may be excluded from the base estimate.
Implementation and scope are decided after reviewing country, platform and store policies.
We review the existing build and server structure before estimating a separate LiveOps scope.
Game development inquiries
Tell us the platform, core gameplay, target schedule and budget. Include reference games or an existing build if available. We review the initial scope against development deliverables and operating responsibilities.