Skip to content
Affaf Imran
All Work

09

Monverse

Solo developer

Monverse, primary view

Multiplayer was considered during development but removed. It was not delivered, and nothing here claims a multiplayer implementation.

01Context

A cross-platform interactive game built solo in Unity for mobile and WebGL.

Solo means the whole stack: gameplay and AI, the interface, the backend behind it, the Web3 integration, the internal tooling, and getting builds out to two very different targets.

02My Ownership

  • Gameplay

  • AI

  • UI

  • Backend

  • Web3

    Integration

  • Tools

  • Optimization

  • Deployment

    Mobile · WebGL

03Engineering Scope

One developer across the full stack, with two build targets from a single Unity project.

Game

  • Gameplay
  • AI
  • UI

Services and integration

  • Backend
  • Web3 integration
  • Tooling

Delivery

  • Optimization
  • Mobile deployment
  • WebGL deployment

04One Developer, Two Targets

Shipping the same Unity project to mobile and to WebGL pulls in two directions: one is a memory and battery budget, the other a download and startup budget. Optimization was continuous rather than a phase, because a change that helps one target can hurt the other.

Working solo means the tooling matters more than it would on a team, since there is nobody else to absorb a slow workflow. Backend and Web3 integration were built alongside the game rather than bolted on at the end.

05Outcome

The client did not release the project.

Development covered the full stack: gameplay, AI, UI, backend, Web3 integration, tooling and deployment to both targets. Multiplayer was explored and dropped before delivery.

06Visual Evidence

Monverse, targeting during gameplay
Targeting and combat gameplay
Monverse, combat against a crowd of enemies

Previous case study

08NeoWorlder 3D Web Viewer

Next case study

10Hotel Tycoon

Back to all work

Monverse case study: Affaf Imran