3D / METAVERSE ENGINEERING
PROPELOO engineers 3D and metaverse platforms — from Three.js and WebGL scene architecture through avatar systems, real-time multiplayer, virtual land and the on-chain asset layer that gives users genuine ownership. Most metaverse projects fail because they build impressive demos and unplayable products. We build the product.
The metaverse projects that failed shared a common pattern: impressive tech demos, empty worlds, no reason to return. The projects that survived — Roblox, Minecraft, Decentraland at its best — had gameplay loops, social mechanics, reasons to come back. A 3D world is not a product. What people do in it is the product. PROPELOO designs 3D and metaverse experiences starting with retention mechanics — what brings users back on day seven — before deciding which rendering engine to use.
Three.js or Babylon.js scene graph design, PBR materials, HDRI lighting, shadow mapping, post-processing effects and Level of Detail (LOD) for performance.
WebSocket-based multiplayer with entity interpolation, lag compensation, authoritative server for game state, Colyseus multiplayer server and voice chat via WebRTC.
VRM avatar support with IK for body tracking, avatar customisation, Ready Player Me integration, emotes and gesture system.
Procedural world generation, user-owned parcels via NFTs, building mechanics, spatial audio zones and teleportation between spaces.
ERC-721/1155 NFT assets as in-world objects, on-chain ownership verification and marketplace for virtual goods.
WebXR Device API for VR headsets (Quest, Vision Pro), hand tracking, spatial interaction, fallback to desktop mode.
Performance is not optional in 3D. A metaverse experience that runs at 20fps on a mid-range laptop has already lost.
60fps on a MacBook Air M1 with 50 concurrent users is the baseline. Every asset, every shader, every physics calculation costs frame time. Set performance budgets before writing rendering code: draw call limit, polygon budget per asset, texture memory limit.
Axiom:
A 45-second loading screen kills retention. Progressive asset loading — show the world immediately at low quality, stream higher quality as users move — is the difference between users who experience your world and users who close the tab.
Axiom:
Real-time multiplayer in 3D requires: canonical state, handling network jitter and packet loss, and preventing cheating on positional data. An authoritative server with client-side prediction and reconciliation is the production architecture.
Axiom:
NFT assets should be renderable as standard GLTF, importable into any compatible world and tradeable on standard marketplaces. On-chain ownership enhances the asset — it should not confine it.
Axiom:
Impact: Three.js for web-first experiences. Babylon.js for complex physics and game-like requirements. Unity WebGL only for teams with existing Unity expertise.
Impact: Colyseus for most metaverse projects — good documentation, schema-based state synchronisation.
Impact: Rapier for complex physics — 5-10x faster than JS physics engines via WASM.
Impact: Ready Player Me for fast deployment and cross-platform identity. Custom VRM where avatar style is a core differentiator.
Impact: Metadata on-chain (ERC-721), 3D assets on Arweave (permanent) or S3+CDN (fast). Never store GLTF on-chain.
Impact: Instanced worlds for most metaverse applications — predictable load per instance, proven pattern from Fortnite and Roblox.
3D conference/concert space with avatar presence, voice chat, screen sharing, interactive objects and NFT ticket gating.
User-owned virtual land (NFT parcels), building mechanics, on-chain asset display and social spaces with real-time multiplayer.
3D game world with on-chain NFT characters/items, P2E mechanics, multiplayer combat and in-game marketplace.
Branded 3D product showroom — photorealistic visualisation, virtual try-on, guided tours and purchasing integration.
3D training environment for manufacturing, medical or safety procedures — VR-compatible, progress tracking, certification integration.
Embeddable 3D avatar SDK — VRM loading, customisation, emotes, React/React Native components.
Stack: Three.js, Babylon.js, React Three Fiber (R3F), WebGL shaders (GLSL), @react-three/postprocessing
Stack: Rapier (WASM), Cannon.js, Three.js AnimationMixer, IK solvers, Tweakpane
Stack: Colyseus, Socket.io, WebRTC (mediasoup), Nakama
Stack: GLTF/GLB format, VRM (avatars), Draco compression, KTX2 textures, Ready Player Me
Stack: ERC-721/1155, wagmi + viem, Arweave, IPFS (Pinata)
Stack: WebXR Device API, Three.js VRButton, hand-tracking, A-Frame
Client-reported positions and game state must be validated server-side. A client that teleports or claims impossible state must be detected and rejected.
When loading NFT assets into the world, verify on-chain ownership at load time. Cache with short TTL. Never trust client-provided ownership claims.
3D worlds with user-uploaded content need content moderation — explicit content detection, trademark violation detection and abuse reporting.
Voice chat via WebRTC requires TURN server authentication, SDP offer validation and monitoring for harassment.
Game servers are common DDoS targets. Infrastructure behind DDoS-protected layer, rate limiting on connection attempts, automatic server respawning.
In-world transaction contracts require full audit before mainnet — same standards as DeFi.
Space layout, interaction design, multiplayer architecture, asset requirements, performance targets.
Scene setup, camera, lighting, asset pipeline, performance monitoring baseline.
Navigation, avatar, interaction, physics — the core experience loop.
Server setup, real-time sync, voice chat, room management.
NFT asset loading, ownership verification, marketplace.
LOD, asset streaming, draw call reduction, profiling on mid-range hardware.
VR/AR support, load testing, production deployment.
Three.js for web-native experiences: no install required, works in any browser, React integration. Unity WebGL for teams with existing Unity expertise or complex game mechanics. Unity WebGL produces large build sizes (50-100MB+) and has poor mobile browser performance. For consumer-facing 3D web, Three.js typically performs better.
A single Colyseus room handles 50-100 users comfortably. Instanced architecture scales linearly — 1,000 users = 20 rooms of 50. Seamless open worlds require spatial partitioning (dividing the world into regions per server) for thousands of concurrent users.
WebXR Device API is the browser standard for VR and AR — works with Meta Quest, Apple Vision Pro (browser), desktop VR headsets. Three.js has built-in WebXR support. A desktop Three.js scene can be made VR-compatible with relatively minimal changes. No app install required.