HTML5 is often the scapegoat for poorly designed apps and games and generally receives more negative press than positive. Despite what others may lead you to believe, it’s still a viable platform for creating games, and more importantly it’s on the way to becoming a commercially viable platform for games.
As founder of a company trying to help pioneer some of the HTML5 game space, I get to see the technology’s adoption first-hand. I’m also able to speak with a lot of folks who are either making the transition to HTML5, have plans to do so, are on the fence, or have no desire at all. Combining my experience with that of others, there are a few things that stand out as necessary steps to commercial success for HTML5 games.
For developers wanting their game on every possible device, HTML5 is ready today – even for games that are more advanced than one might expect. Not only is HTML5 viable for games akin to early iOS games, we’re starting to see games pushing the bar even further on mobile Zirma is a good example of this. Though the graphics might not be as pleasing as most hit iOS games, the game itself is a pretty advanced RTS. Not to mention it was built by a single programmer.
While quality games can be made today, what we haven’t seen is a commercial hit HTML5 game. Could a commercial hit happen with the current state of HTML5? Yes, but there are a few things that will help make it more of a common occurrence.
Here’s what I think we need to see for HTML5 to make the leap to a platform with an abundance of commercially successful games.
Improved Performance on Mobile
One of the main issues with HTML5 has always been performance on mobile devices. It has certainly gotten better in the past few years (on the order of magnitudes), but there is still room for improvement.
CocoonJS / Accelerated Canvas App Game Interface
The tech for each of these are still fairly new and rough around the edges, but could prove to be a pivotal step to higher quality games that have commercial success.
Further Browser Adoption
While most HTML5 related technologies will run smoothly regardless of the browser (assuming it’s not IE8 and down), there are still features certain browsers have been slow to implement.
The most notable features are WebGL and Web Audio. It’s no surprise that the ‘late-bloomers’ for each of these are Internet Explorer and some of the mobile browsers. WebGL taps into the device’s GPU for better performance and the potential for console-quality games in a browser. The Web Audio API allows for more control over the device’s audio than the standard <audio> tag provides.
Internet Explorer is finally supporting WebGL with IE11 and Web Audio will hopefully be fully supported within the next year.
Another (even newer) technology that pertains to games is WebRTC – particularly the data channels. WebRTC channels make client to client UDP communication possible. Google used it for their CubeSlam demo back in June. It’s supported in Firefox and sort of supported in Chrome, though it may be a while before IE or Safari adopts it.
Adoption is a bit of a tricky issue with HTML5 since it relies on various companies implementing based on a standard. Fortunately Mozilla and Google have a strong relationship for these things and Microsoft is catching up some.
More Investment Into Better Tools
As CEO of an HTML5 game tools company, I realize making this claim is like a retailer saying “people should be spending more to help the economy”… hopefully my argument is sound regardless.
For any platform to be successful, the tools need to be great – tools for creation, distribution, retention, and commercialization. It’s hard enough to create a game. It gets to the point where it’s too hard if you have to do everything yourself and build from the ground up.
LinkedIn is one of the high profile companies that has stepped back a bit on HTML5. In a recent interview, Kiran Prasad, LinkedIn’s senior director for mobile engineering, stated
It’s not that HTML5 isn’t ready; it’s that the ecosystem doesn’t support it. … There are tools, but they’re at the beginning. People are just figuring out the basics.
Some of the tools rely on the browser vendors: Microsoft, Google, Apple and Mozilla, but a big chunk of the ecosystem is going to come from startups. With games, the ecosystem is primarily composed of Game Creation tools, Retention / Monetization tools, and Distribution.
Here’s where we’re at in 2013, and the hope is that some of these companies – and any newcomers – will help pave the way to more commercial HTML5 success. I’m ignoring the companies that have already been acquired / acquihired, or have transitioned more towards native game tools.
Most of the money raised in the space has been for companies with an initial focus of helping developers create great games.
Turbulenz is a UK company with $5 million in funding and a very impressive toolset for developing games.
There are plenty more game engines available to developers. Most of these are bootstrapped, but that doesn’t mean they are worse than the two above. The game creation area of tools is the ground level for the ecosystem, so these companies need all the help they can get.
Retention / Monetization Tools
While there are loads of companies trying to help developers create games, the higher-level tools are a bit more sparse – at least in companies that have raised money.
Clay.io – disclaimer: I am a founder. We haven’t raised any money and I’m the only one who has been working full-time on the platform in the past 20 months. That of course makes things very difficult.
Fortunately, I have most of the necessary skills to build the company both from a product and business perspective – we’ve actually grown to be the marketplace with the most HTML5 game developers (3,000+) and most-used high level tools for these games.
I suppose that’s a good indicator of what the tools ecosystem is like right now – one person has built the leader in those two categories… However, what I’m doing is not scalable. It’s time to take things to the next level, and that involves raising a seed round and expanding the team.
Scoreoid – raised a small seed round ($100k). They’re not completely specific to HTML5, but they are the second-most used toolset for the games.
Google Play Services – contrast to the first two, Google obviously has plenty of money and resources to work with. However, their vision of the future revolves a lot around Google Play, so I don’t see this being too much different from Apple’s more restricted Game Center. Yes, it’s cross-platform, but only to an extent…
For distribution, I’m not sure whether it will be a startup who makes the biggest impact, or an existing big player. A smaller company / startup end would make sense in that they would be willing to take a bigger risk on HTML5 and try to bring something completely new to the table. On the other hand, it’s quite a bit easier to distribute games if you already have a big name and plentiful resources.
Any serious company that gets into HTML5 gaming wants to be a part of distribution in some way or another. Of the companies I’ve already listed – Turbulenz, GameClosure and Clay.io are all taking different approaches to make this happen. You can also add Artillery and Ludei to the mix.
Turbulenz’s approach is to have great game creation tools to get quality developers using their tools to make games. Once those games are developed, they can be played directly from Turbulenz’s site. GameClosure and Ludei are more focused on distribution through native mobile app stores once the games are created with their tools. Artillery is building a game in house with hopes of it being a hit – then rolling out tools for other developers to distribute with. Clay.io is more focused on reaching as many developers as possible. Reaching them through high level tools that are non-specific to creation tools, a secondary marketplace, and distribution focused on places where HTML5 apps work without wrappers.
Which approach will work? Who knows. It could very well be one not listed.
Why Invest Now?
From the market’s perspective, better tools are needed, which means the ecosystem needs more financial support. Most investors aren’t going to care as much about that as they are for seeing that HTML5 can be properly commercialized. It certainly doesn’t help that there have been high profile failures with HTML5.
The tech has caught up for the most part. Not only that, but Major projects that have been in the works for a while like Firefox OS are Tizen are finally seeing the light of day.
Google seems poised to do something similar soon by either a) treating HTML5 apps on Android as first class citizens with no wrapper required or b) start phasing out Android for Chrome OS. The latter might seem a bit far fetched with the large ecosystem Android has built, but the OS is extremely fragmented and Google has more control with something like Chrome OS.
Big things are happening with HTML5 and it has matured to an extent but there are still so many open holes for companies to fill and do very well with.
More Games, Fewer Demos
HTML5 games have somewhat of an aura around them of being mostly comprised of cool demos. The major browser vendors have cranked out some impressive demos like Google’s CubeSlam, Mozilla’s BrowserQuest and Microsoft’s LookAround. Unfortunately, demos don’t make money, so being known for “the tool used to make that one demo” isn’t a good thing.
Each of the demos is built in part as a marketing tool for the respective vendor, meaning they often don’t take advantage of some of the main benefits of HTML5, but I’ll touch on that more later.
Google and Microsoft have tried porting successful games to HTML5 with Angry Birds and Cut the Rope – but each attempt focused on just the desktop web, and neither brought anything substantially new to the table. On one hand Angry Birds Chrome could be considered a success with 10MM+ installs on the Chrome Web Store, but I really would have liked to see it prove HTML5 as commercially viable and convince more developers to use it.
Building for HTML5, Not with HTML5
Just as we still see too many demos and not enough full-featured games, there’s also too much emulating native mobile games.
HTML5 isn’t another way to make mobile games. Yes, you can make mobile games with the technology, but HTML5 – The Web – is so much more than that. I have an entire post dedicated to this because I think it’s so important.
Developers need to adopt the mindset that HTML5 is different and build games accordingly. Otherwise HTML5 competes directly against native mobile in areas like performance and it’s never going to win that battle.
Distribution is pretty commonly cited as a concern for HTML5, but it’s not something I’m too worried about. Not only can you use a wrapper to distribute games to any possible app store, more stores are accepting HTML5 apps and games as first class citizen with access to native APIs.
The fact of the matter is, most app stores are already completely saturated with games. The web offers the unique advantage that you don’t have to go through an app store, and games can be played straight from a browser or webview – that’s huge. You can tap directly into Facebook and Twitter’s virality and have players jump into the action right away. Of course, this does require a bit different of a mindset when designing and developing the game.
Distribution options are there – it just needs to be proven to studios that a well-distributed commercial HTML5 game can be made.
With that said, a few things could be done to improve distribution and retention for games.
Better “Save to Device” Options
Though it might seem insignificant, having some sort of “Save to Device” method for mobile web games is critical for player retention. App Store games are played frequently because they have permanent icons on the device – web games don’t necessarily. This exists on iOS and is fairly easy to use, but Android support is a bit lacking. Firefox OS has the best support, but that is expected. I’d really like to see Android put more emphasis on a similar feature.
Firefox OS and Tizen Adoption
The approach Mozilla is taking to get Firefox OS off the ground is targeting the billions of people who don’t have smartphones in developing parts of the world. We won’t know if this is successful for a while, but it could mean massive distribution for developers of HTML5 games.
Similar to Firefox OS, Tizen is a mobile operating system that heavily supports HTML5. It’s a Linux Foundation project backed by Samsung and Intel, so it also has some major oomph behind it.
Either one of these operating systems gaining traction would make distribution of HTML5 games that much better.
A Success Story
The biggest factor in HTML5 being commercially viable at a large scale is a success story. For most platforms it takes at least one hit game before mass adoption follows. Social gaming had Zynga with Zynga Poker and Yoville before the rest of the industry started caring about social games. iOS had games like Super Monkey Ball very early, but Doodle Jump and Angry Birds specifically caused a huge flock to iOS – everyone from Indies to companies like EA.
Like investors, developers and studios often have a herd mentality and will start working with a new platform when they see others having success. The early herd can still benefit, but the first commercial success has a bit of an unfair advantage.
I’m not really sure who this will be for HTML5. On one hand, it could be an existing player in the mobile/Flash games space, but I’m inclined to think it will be someone new. Either a company that has raised money so they have the resources to pull of something great, or one of the studios that continually churns out game after game until they really figure out how to make the most of HTML5.
Of course, it could very well be one of the major players. EA is working with HTML5 on a few projects, Zynga is the same. The successful Java-based MMO, Runescape (220 million registered accounts), has gone all in with HTML5 and WebGL for their latest version.
Success stories are critical to drive adoption, and fortunately it just takes one.
With all that said, HTML5 is ready right now. The tools aren’t quite at the level of other platforms, but they’re good enough. Support for non-WebGL games can be found across every modern device and browser. Quality games can already be developed that work on all devices. Performance on desktop isn’t an issue; on mobile there is a bit of extra work, but it can be done. Games can already be distributed to every app store and various other means. HTML5 is ready – but it make take some time before we start seeing that hockey stick graph iOS and Android had for adoption.
If there’s any way I can help – with what I’ve learned of the HTML5 game space, or anything else – don’t hesitate to reach out to me at firstname.lastname@example.org.