Challenge
NativeGaming had an ambitious vision: a social casino MMO that would redefine the genre — full 3D world, social mechanics, and jackpot systems where everyone has a real chance to win. They had an IP, an outsourced development team, and funding. What they didn't have was game development experience.
When I came in, the project had fundamental issues:
- Client-side business logic with insufficient randomness — a non-starter for any casino game
- No server-authoritative architecture — the foundation wasn't trustworthy
- No complete game loop — features existed in isolation without connective tissue
- Outsourced team lacking senior experience — quality and architectural decisions suffered
- No bridge between the IP owner's vision and the dev team's execution
Solution
Phase 1: Assessment & Restructuring (2022–2023)
The first six months were a full technical and organizational restructure:
Technology stack overhaul:
- Introduced PlayFab for player accounts, data, and backend services
- Moved all sensitive logic (spin results, rewards, jackpots) to Azure Functions — proven, scalable, and properly authoritative
- Established server-authoritative patterns across the entire game economy
Team restructuring:
- Demanded senior developers be added to the outsourced team — resolved ongoing quality and architectural issues
- Brought in an experienced VFX artist to address visual quality gaps
- Established weekly syncs and proper documentation practices to bridge the IP owner and dev team
Phase 2: Full Development (Mid 2023–2025)
With the foundation solid, I directed ongoing development:
- Oversaw the complete game loop implementation
- Managed design iteration while maintaining technical integrity
- Coordinated between NativeGaming leadership and the development team
What Made This Hard:
The hardest part was restructuring while building. The tech stack needed fundamental changes, but development couldn't stop. Every architectural improvement had to be sequenced carefully to avoid blocking the team. On top of that, regular design changes and requests from the IP owner required constant re-prioritization without derailing the roadmap.
Results
- Tech stack: Fully restructured from client-authoritative to server-authoritative
- Team: Senior developers added, VFX quality improved, communication processes established
- Timeline: 6-month restructure, followed by 2+ years of directed development
- Status: PixiuWorld is now live; project handed over for ongoing operations
-> later expanded into PixiuTap
