Indie perspective

on Web games

W3C Workshop on Web Games

Andrzej Mazur@end3rEnclave Games
W3C Workshop on Web Games, Redmond, WA, June 27th 2019

Andrzej 'End3r' Mazur

Andrzej Mazur

Logos

2011 vs 2019

2011

W3C 2011

W3C workshop at the onGameStart 2011 conference
HTML.next for Games, Warsaw, Poland

2012

Is HTML5 ready for gaming?

Canvas performance

Performance

Way worse than native

Crappy audio

Audio

Too many formats, play/sync issues

Working offline

Offline

Web Storage, AppCache, IndexedDB, Web SQL

Drafts of Web APIs

Web APIs

Gamepad, Pointer Lock, Fullscreen, ...

Development tools

Dev environment

Borrowed from front-end

Monetization

Monetization

Go native or go home

2019

Good news

It works! So, what now...?

Web vs Native

Native

Steam

Packaging to iOS, Android, Steam, ...

Web

Publishers and platforms

  • Focusing on mobile devices
  • Using benefits of PWAs

Indies vs Studios

Small indies

Stack

Fast hyper-casual mobile experiences

Bigger studios

Quake4

WebGPU, WebAssembly, WebXR,
hundreds of MBs of assets

Survey!

Asked the community
for feedback

So many different results...

  • Too many packagers and preprocessors
  • Need of dev tools focusing more on gamedev
  • More tutorials, courses, materials
  • New platforms oversaturating extremely quick
  • Not enough support for indie devs
  • Native 2D and 3D math modules
  • SharedArrayBuffers for multi-threaded games
  • Discoverability and monetization
  • Discoverability

    2011 vs 2019

    Front Invaders
    500 games

    Monetization

    • Licensing, subscription, revenue share, IAPs
    • Freelancing, client work
    • "Making a decent living" vs "becoming rich"
    • Protecting the assets from theft

    Summary

    • Technology is sufficient (but can be improved)
    • Discoverability issues (saturated market)
    • Lack of solid monetization options

    Thank you!

    Let's talk!

     

     

     

    Andrzej Mazur@end3rEnclave Games

    Ender Efka @end3r