Services

What I build

• Playable ads for Facebook Instant Experience, Google Ads UAC, TikTok, AppLovin, Unity Ads, Mintegral, IronSource, Vungle, and Moloco. MRAID-compliant bundles, end-card variants, and multi-language builds. High-converting playable ads, built to each network's specs.
• HTML5 games and browser games for branded microsites, casual gaming portals, social platforms, and embedded web players. Phaser, PixiJS, Cocos Creator, Three.js, and vanilla JS, with the engine picked to fit the brief. Custom builds, not template restyles.
• Kiosk experiences for retail, trade shows, and brand activations. Windows IoT, Android tablet, and iPad deployments, offline-first.
• 3D HTML5 games and WebGL games in Three.js, with PlayCanvas or Babylon.js on request. Performance-tuned for mobile GPUs and tight ad-slot budgets.
• Unity game development for 2D and 3D games, when a native or cross-platform build fits the goal better than the browser.
• Reward, skill, and gamification builds for Shopify stores: spin-to-win, scratch, and skill-based reward games that plug into loyalty and rewards flows.
• Educational web games and mini games, including in-app mini games for mobile apps and product onboarding.
• Mobile apps and games (native or hybrid) for utility apps and game-adjacent product builds, plus mobile game development for Android and iOS.
• Games for new platforms: YouTube Playables, Discord activities and games, Reddit games, and Telegram bots and mini apps. Same HTML5 and JavaScript core, packaged for each platform's SDK.

How I work

1. Discovery (free, 20 to 30 min). A call or async brief exchange. I ask about target network and surface, file-size budget, asset status, timeline, and variants, and you get an honest read on whether the project fits.
2. Spec and estimate. A written scope with the technical decisions called out (engine, file-size strategy, asset pipeline). Fixed-bid projects get a not-to-exceed number; hourly work gets a sprint-by-sprint estimate.
3. Build. Weekly check-ins, with milestone demos every couple of days on short projects and weekly on longer ones. You can see the build at every stage.
4. QA and network packaging. Device-matrix testing (iOS Safari, Android Chrome, mid-tier devices at least two years old), MRAID validation, and network-specific zip and manifest formats.
5. Handoff. Final assets, source code (license per agreement), and documentation of the network-specific build process, so your team can re-package later without coming back to me.

Engagement models

Three ways to work together. Pick the one that fits.

• Fixed-bid project. One quoted price for a defined scope. Best for clear briefs with stable requirements, and common for single playable ads, kiosk installations, and branded microsites.
• Hourly. Billed in weekly sprints with a rate sheet shared up front. Best for evolving briefs, ongoing partnerships, or work where scope discovery is part of the project.
• Retainer. Capped hours per month for ongoing partner relationships. Best when you ship three or four projects a quarter and want continuity.

For pricing details, reach out via the contact page. Rate depends on engagement model, project duration, and IP/licensing terms.

Tech stack I ship in

• Game engines: Cocos Creator, Phaser 3, PixiJS, Three.js, Babylon.js, vanilla JS canvas/WebGL.
• Mobile: Swift / Kotlin (native), React Native / Flutter / Capacitor (hybrid).
• Backend (when needed): Node.js, Cloudflare Workers, REST / WebSocket. Postgres or SQLite for persistent state.
• Tooling: TypeScript, Webpack / Vite / Rollup, Jest / Vitest, GitHub Actions for CI.
• Asset pipelines: Spine, DragonBones, Lottie for character animation. Compressed textures (Basis / KTX2) for 3D. AVIF/WebP for image delivery.

IP, NDA, and licensing

• IP transfer. Final deliverables transfer to you on payment in full. I keep the right to show finished work in this portfolio unless an NDA explicitly forbids it (in which case I expect to be told before kickoff).
• NDAs. A standard mutual NDA is fine. I don't sign one-way NDAs that prevent me from naming you as a client (that defeats the purpose of portfolio-building for both sides).
• Third-party assets. If a project uses paid library code (a Spine runtime, a paid Phaser plugin), the licensing cost passes through at cost.
• Source-code license. By default you get exclusive rights to the final source. If we're building a template you plan to resell, that's a different conversation, and it gets priced differently.

What I do not do

• Casino / real-money gambling games.
• Pure design / illustration work without a development component.
• App-store-review repair services.
• Mass-volume "playable ad farm" output. I do bespoke builds, not template-restyling at scale.