Game development for multiplayer, mobile and the webGame development for multiplayer, mobile and the web

It depends on the kind of game. A single-player offline game with simple rules is far less work than an online multiplayer game that needs an authoritative server, matchmaking, reconnection, ranking and a shop. Bot intelligence, the number of platforms and the amount of custom art matter too. We write the rules and scope down first, then estimate phase by phase, so you can start with a small but complete version and add social and revenue features later.

Fairness comes first: no client may see anyone else's cards, so game logic must run on the server and each seat receives only its own hand. Then come the local rule variations players know by heart, where any mistake destroys trust. You also need to handle disconnects mid-hand and replace departed players with bots without stalling the table. In Hokm, Shelem and Hamdor we solved all of this with an authoritative server and a shared rules engine.

An Android app gives smoother play, notifications, reliable offline mode and a place in app stores. A web game opens from a link with no install, runs on iPhone and desktop, and is excellent for sharing and early user acquisition. You do not have to choose: in Hamdor the same Kotlin code builds the Android app and compiles to Kotlin/Wasm for the browser, at 2.7 MB after brotli compression.

In multiplayer game development the authoritative server is the referee: the client only requests a move, the server checks it against the rules, updates the state and sends each player only what they are allowed to see. It is the only serious defense against cheating. We build servers with Ktor over a persistent WebSocket with compact ProtoBuf messages, make reconnecting and resuming the default, and keep state in PostgreSQL.

As smart as the game and budget allow. For easy levels, rule-based bots are enough and play naturally. For card games with hidden information, methods like PIMC sample many possible opponent hands and pick the move with the best average outcome; our hard Hokm and Shelem bot works this way. The key is that bots and server share one rules engine, so a bot can never make an illegal move.

Yes, and for an online game this matters as much as the build. We deploy servers with Docker, a backup before every release and automatic rollback on failure, monitor errors and load, and give your team a live admin console with match, shop and revenue reports. Seasonal events, new games and balance tuning can continue under a maintenance agreement. The source code and infrastructure always belong to you.