GameTime / PisoNet
A purpose-built PisoNet platform for managing customer wallets, PC sessions, device availability, cashier operations, closing reports, audit history, and Windows station access from one central server.
Role
Product Designer, Systems Architect, Full-Stack Developer, Desktop Application Developer
Platform
Server + Windows Client
Status
Live Beta
Year
2026
Operational system with private deployment details
The portfolio focuses on the architecture, workflows, and product decisions without exposing customer records, credentials, network secrets, or private deployment configuration.
Overview
GameTime / PisoNet replaces a fragmented gaming-station workflow with a centralized server and lightweight Windows client. The server acts as the source of truth for users, wallet balances, ledger entries, devices, sessions, and operational reporting.
Each station runs a Windows client that authenticates the customer, starts and monitors sessions, communicates heartbeats to the server, warns about low remaining time, and returns to a controlled gate state when a session ends or the server becomes unavailable.
Problem
A multi-PC gaming shop needs reliable control of paid time, balances, devices, cashier activity, and closing reconciliation without manually managing every station.
- Track paid time across multiple PCs
- Prevent conflicting active sessions
- Keep wallet balances consistent
- Know which devices are available
- Handle customer top-ups and adjustments
- Recover from client disconnects
- Maintain accounting history
- Produce daily and monthly closing reports
- Keep station access controlled after time expires
Solution
The system separates the central business state from the station interface. PostgreSQL-backed server logic owns wallet and session state, while the Windows client acts as the controlled station endpoint.
This makes the system easier to scale from a small shop to additional PCs because a new station can be registered as a device and run the same client without creating a separate accounting system.
Core workflow
The system connects cashier activity, customer identity, paid time, and station control into one lifecycle.
- 1
Register customer
Create a customer and wallet identity.
- 2
Top up wallet
Record cash or manually confirmed QR payments in the ledger.
- 3
Assign credentials
Provide wallet/card identity and secure setup flow.
- 4
Log in at station
The Windows client validates the customer and device.
- 5
Start session
The server creates the active session and calculates remaining time.
- 6
Heartbeat
The client periodically reports that the station is still active.
- 7
Monitor balance
The client displays remaining time and low-time warnings.
- 8
End or expire
Sessions end safely or return to the locked gate state.
- 9
Close the day
The owner reconciles cash, QR records, sessions, and exports.
System areas
The platform is divided between central administration and controlled Windows endpoints.
Server and administration
Central source of truth for shop operations.
- Users
- Wallet ledger
- Devices
- Active sessions
- Vouchers
- Audit log
- Closing reports
- CSV exports
Windows station client
A controlled client for customer login and paid-session execution.
- Wallet/card login
- Gate mode
- Session panel
- Heartbeat
- Low-time warning
- Server-offline state
- Owner exit
Reliability layer
Designed to tolerate normal client failures and reconnect conditions.
- Heartbeat monitoring
- Stale-session handling
- Watchdog
- Autostart
- Explicit offline state
- Safe session termination
My role
I designed the operational model, server/client architecture, wallet and session workflows, admin experience, reporting model, Windows gate behavior, and deployment approach, with AI-assisted implementation and iterative real-world testing.
Architecture
Technology stack
Technical challenges
Session state across server and PC
Designed heartbeat and stale-session rules so the server can distinguish an active station from a disconnected client.
Controlled Windows access
Implemented a lightweight gate mode that returns the station to a locked state when paid time ends.
Wallet accounting integrity
Kept money and time-related state tied to ledger and session records instead of relying on client-only balances.
Multi-device deployment
Added machine-name device identification so one published client build can be copied across multiple PCs with minimal configuration.
Closing and reconciliation
Built daily closing and CSV export workflows so operational totals can be checked against physical cash and payment records.
Quality assurance
Build integrity
- Prisma schema validation
- TypeScript checking
- Production builds
Functional validation
UI and live validation
Results
Qualitative workflow outcomes
Server + client
Centralized business state with Windows station endpoints.
One source of truth
Wallet and session records are maintained centrally.
Multi-PC ready
Additional stations can be registered as devices.
Daily + monthly
Operational data can be exported for reconciliation and review.
What this project demonstrates
GameTime / PisoNet demonstrates a practical client-server system designed around a real operating environment, where reliability, accounting integrity, and ease of adding additional stations matter as much as the interface.
- Design the business ledger before the interface
- Keep clients thin and server state authoritative
- Treat unreliable networks and power conditions as real product requirements
- Build reporting into the operational system rather than adding it later