PROJECT CASE STUDY · MOBILE DEVELOPMENT
ChessMate
An Android chess game built with Flutter. Play against a Stockfish-powered opponent, share a device for local games, or create an online room with real-time moves and chat.

At a glance
- Platform
- Android
- Client
- Flutter and Dart
- AI opponent
- Stockfish engine
- Online backend
- Node.js and WebSockets
- Latest release
- v1.0.143 · Android APK
- Automated build
- GitHub Actions workflow
The problem
A mobile chess game has to manage legal moves, game outcomes, clocks, and player interactions while keeping the experience understandable on a small screen. Online play adds another challenge: both players need a consistent game state even when connections are interrupted.
Features implemented
Play against AI
Easy, Medium, and Hard difficulty options with Stockfish engine integration.
Local 2-player
Two people can play on the same Android device.
Online multiplayer
Create or join room-code games with server-authoritative move validation, real-time synchronisation, and reconnection support.
Live match chat
Room-scoped messages, quick replies, timestamps, unread counts, message validation, and rate limiting.
Chess rules and match flow
Legal move handling, checkmate and draw detection, clocks, resignation, draw offers, and rematches.
Android release workflow
GitHub Actions runs project checks and builds a downloadable ARM64 Android APK release.
Technical architecture
The Flutter app manages the interface and local game experience. Stockfish provides computer-opponent play. For online matches, the app communicates with a Node.js server over WebSockets; the server uses chess.js to validate moves and maintain each room's authoritative game state. Online room and chat state is held in memory by the server.
Testing and delivery
The repository includes Flutter tests and an automated APK build-and-release workflow. The latest published release is v1.0.143, with an ARM64 Android APK attached.
Player journey and state management
The game supports three entry paths: choose a Stockfish difficulty for a solo match, start a local match for two players on one device, or create/join an online room. During play, the interface coordinates board position, turn, legal actions, clocks, and end-of-game status. Online play adds room membership, server-confirmed moves, reconnect handling, and chat state without treating the client as the authority for chess rules.
Engineering decisions
Separate game modes
Local play and online play have different synchronization needs, while sharing the chess-focused interface.
Server-side validation
The online server validates moves with chess.js so clients cannot independently decide the authoritative board state.
Room-scoped communication
WebSocket rooms isolate match updates and chat to the relevant players.
Release automation
GitHub Actions checks the project and packages an Android APK for distribution.
Scope and limitations
Online room and chat state is held in server memory, so it is designed as a lightweight multiplayer service rather than a persistent tournament platform. A production expansion could add durable match history, accounts, and broader device testing.
What this project demonstrates
- Building an Android application with Flutter and Dart.
- Integrating a native chess engine and managing rule-driven game states.
- Designing a real-time client/server feature using WebSockets.
- Implementing room-scoped messaging and server-side input validation.
- Automating Android builds and release publishing with GitHub Actions.