Future Proof: HTML5, Native Client and the Battle for the Browser

Massively Fun, Pixel Lab and Zipline Games on the next great gaming platform

The boom in social and mobile gaming has irrevocably altered the landscape of the games industry, but in this business opportunities to rest on your laurels are few and far between.

The reassuring clarity offered by the dominance of the iPhone and Facebook has started to give way to fragmentation: the meteoric rise of Android, the nascent promise of Windows Phone and the burgeoning tablet market on one hand; the faltering first-steps of Google+, the Western spread of Asian companies like Tencent and Gree, and breakaway attempts from key players like Zynga on the other.

For game developers, this means more work, higher costs and greater complexity, with no guarantee that the extra risk will carry a better chance of reward. With more hardware and distribution options emerging every few months the addressable market is expanding in new and inscrutable directions. Gaming is no longer corralled into discrete and largely isolated platforms; users want to flit from mobile to web to console to tablet to PC, so the key challenge for any game developer is to get their product on as many devices as time and resources will allow.

In that respect, the promise of HTML5 is a sort of Holy Grail: game experiences once only available through native apps and plug-ins, now achievable seamlessly through the browser on any device that can support one - mobile, PC, tablet, smart TVs, you name it. Write a game once, take it anywhere.

HTML5: The Good

In a recent survey of almost 2200 app developers, commissioned by Appcelerator, 79 per cent confirmed that they would be integrating HTML5 into their products in 2012. The various technologies that comprise HTML5 are still being discussed and refined by standards organisations and browser vendors, but for those involved in that process its place in the future of game development is all but assured.

Kevin Moore is one of those people. He is a veteran software engineer and a partner in Pixel Lab, the app developer behind the HTML5 pool game Agent 008 Ball and the HTML5 edition of mobile hit Cut The Rope. The latter game, in particular, illustrates a key point about HTML5: it may not be able to support Call of Duty exactly, but it's already more than capable of producing the sort of games that millions of people have paid millions of dollars to play.


Massively Fun's Word Squared is simple, but it leverages many of HTML5's unique strengths.

"The set of experiences you can create now that work really well across mobile and desktop and TV, on whatever default browser people are using, without installing a plug-in, without installing an app, the quality of those experiences Is getting much better," Moore says.

"The browser is fine if you want to do Words With Friends. You don't need much more than a browser can provide. So why limit yourself to having three different engineering sets to understand - building iPhone and Windows Phone and Android apps - when you can just go HTML?"

Massively Fun's Grant Goodale frames HTML5 in much the same way. Right now, Massively Fun's MMO/word-game hybrid, Word Squared, is perhaps the most convincing demonstration of HTML5's unique strengths. The design is simple, certainly, but it offers seamless cross-platform interaction regardless of which devices the players are using. And if a new hardware platform were to emerge in the coming months, Word Squared could be ready for distribution almost immediately.

These qualities can be neatly summed up by one word: reach, and in that respect nothing else comes close to HTML5.

However, from Goodale's point-of-view there is another, quietly seductive quality to HTML5: it allows developers to leap-frog the administrative problems and prohibitive costs associated with releasing products on closed platforms like Facebook, iOS and Xbox Live.

"I fully expect a lot of small developers to be very gung-ho about HTML5," he says. "Our game designer has been working on a variety of platforms for about 20 years. He's a veteran of the console wars, and back then it was a couple of million dollars to get your foot in the door. The manufacturing and distribution costs are obscene.

"Then along came the web and Flash, and we thought, 'Oh great, we're free. We can publish our games anywhere we like. We're free of this tax to just put out a game. And then the web became Facebook, and all of a sudden it's a 30 per cent tax on everything that happens."

This is really the big browser companies recognising that the browser is the next entertainment platform. This is the war for the desktop, the mobile device and the couch

Grant Goodale, Massively Fun

"Getting to skip app stores, especially in mobile, is huge," adds Moore. "In terms of how you think about monetising, in terms of the restrictions you have, in terms of update cycles; I've heard crazy things about how long it takes to update a game on Xbox, and the cost. So for me there's a pull to getting out of native apps, because of the overhead, and [HTML5] technology is moving so fast... It's so clear that this is the fastest moving area in development."

For Moore, the ease of distribution is also a major draw. Where plug-ins from company's like Unity have under-performed in terms of conversion rates, with HTML5 the developers' mechanism for deployment is a URL - something that virtually anyone who has used the internet can understand.

"You have to tweak [the app] so that it downgrades nicely on the iPhone, and you have to tweak in Opera, and tweak in Internet Explorer, but the upside is that you can just send someone a URL - that's substantial," he says.

"Maybe you won't target a first-person shooter there, but if you're making a casual game, a card game, or even a 2D scroller, I think we're absolutely at the point where it's realistic to target the browser. And we can skip the Apple App Store and the Android app store, and whatever crazy Windows 8 approval process you have to go through."

In terms of audio, graphics and many of the usual metrics for judging product quality HTML5 falls short, but Goodale regards the notion that it isn't 'good enough' for games as erroneous - it's just good at a specific set of of things. Despite his efforts on Word Squared, however, Goodale believes that HTML5 still needs a "marquee experience"; a game that can highlight the potential of the platform in the same way that, say, Wii Sports did for the Nintendo Wii.

"Once we have that, I think you'll see the pace of innovation quicken. I think you'll see developer adoption quicken."

HTML5: The Not So Good

Exactly when that will happen is another matter. Indeed, the pace of innovation is a major pain-point with HTML5, and not due to a lack of trying. Google and Firefox can both develop APIs to improve audio, for example, but they need to be scrutinised and agreed upon by standards organisations before either can fall under the HTML5 banner.

"It's a fairly nascent platform with a lot of stakeholders, so you're looking at a world in which one browser manufacturer can absolutely fix web audio in the span of six weeks," Goodale says. "But if you want to do that in a standards-type fashion, if you want everybody to agree on it so the platform doesn't fragment beyond recognition, then you have to talk about organisations like the W3C [the World Wide Web Consortium], and suddenly things slow down. This is nothing new - we've been dealing with this in the consumer web world for decades at this point.


HTML5 is already capable of producing casual games like Cut The Rope.

"We understand where the boundaries are, we know what the issues are, and yes, it is definitely slower going than a lot of us would like. But there's a community group for gaming that's being run by the W3C: Google, Mozilla, Internet Explorer, Opera, virtually every major browser vendor is at these meetings - Apple being the notable exception.

"This is really the big browser companies recognising that the browser is the next entertainment platform. This is the war for the desktop, the mobile device and the couch."

According to Moore, discussions currently in progress include WebGL support, APIs for tilt-control, gamepad support and full-screen modes, and many more; So many, in fact, that if "even half of those make the mainstream in the next 12 months, HTML5 is going to be a spectacular bet for gaming. No question."

For Todd Hooper, CEO of Zipline Games, 12 months is a long time in game development, and particularly in smartphone and tablet development - the main focus for HTML5 games at present. Ultimately, the new iPad doesn't have a quad-core A5X processor and retina display just to make Cut The Rope or Words With Friends look sharper. The rate of change in smartphone and tablet hardware is fundamentally altering what even casual consumers expect from their games, and Hooper believes that HTML5 won't progress quickly enough to close the gap.

"You can get a dual 1Ghz core in a phone now," Hooper says. "The new Samsung Galaxy and the new Droid Razr - these are incredibly fast phones. There's no doubt that, with what you can do with those phones, you're going to want native performance to do it, and you're going to want to raise the bar for all games. HTML5 just can't do that for you. People talk about technical workarounds, but once you head down that path you may as well be doing native development."


This infographic, provided by Zipline Games, illustrates many of the current problems with HTML5. Click it and see.

Hooper has been vocal about his doubts over HTML5 as a tool for game development in the past. Indeed, the last time we talked he dismissed the idea as "hype", but while his complaints elicit vigorous defences from both Moore and Goodale, there's a pertinent truth behind the provocative language. HTML5 may serve the needs of the developer, but Hooper argues that it is fundamentally out of step with the needs of the consumer.

"I think it's a dream. I think that's a beautiful dream, but it's still a dream. We have a top 30 game on Android right now; if people want to buy things in the game they press a button, it goes to their Google Wallet, and they give us money. If that was an HTML5 game I'd have to write all that stuff from scratch and people would have to whip out their credit cards. So users have to learn that there's a new way to pay for these games, and frankly, the users seem pretty happy with the status quo.

"A lot of the dream of HTML5 is write once and run anywhere, and to escape from the tyranny of the app stores. I mean, they're noble goals, but in the real world today I'm not sure how relevant they are. Maybe two or three years out it could be more interesting, but today it's really tough to make that case.

"There's a lot of work involved in billing, and app developers now are really spoiled with Apple and Google taking care of that for you. And taking care of the credits and the refunds. I personally think, with where I'm at now, the 30 per cent is worth it."

Native Client: A Challenger Appears

One of the great unknowns with HTML5 is discovery. The dissatisfaction with the 30 per cent cut demanded by many closed platforms is motivated by the increasing difficulty developers face in getting their products noticed. To a large extent, that 30 per cent is an entry fee for access to an established marketplace, but Goodale and Moore believe the sheer number of products, the growing influence of entrenched players like Zynga and Rovio, and the abrupt closure of viable distribution methods has eroded that benefit to the point where there's little difference between iOS and Facebook and the open web.

They have a point, but finding an audience is still problematic, and at present there are no ready-made solutions for HTML5 developers seeking to cut out the middle-man. What's more, if consumers are content with iOS, Android, Facebook and similar services - as Hooper suggests - there's precious little motivation for a third-party remedy to emerge.

For Hooper, a more compelling browser solution for game developers can be found in Google's Native Client [NaCL]; a sandboxing technology that allows native code to run safely in a web page with no plug-in and relatively little investment and effort on the part of the developer. Bastion and Mini Ninjas are already available on the Chrome web store, while From Dust is due for release next month.


Google's Native Client can bring sophisticated, processor-intensive games like Bastion to the browser without a plug-in.

Seeing games of that complexity and visual quality work almost instantaneously in a browser is a difficult experience to shake - "impressive" doesn't do it justice, and major publishers like Ubisoft and Square Enix have responded with great enthusiasm. And the benefits don't stop there: NaCL is free, Google will host the games on the Chrome store for free, developers can monetise any way they see fit, and if they implement Google Wallet they'll be charged just 5 per cent per transaction.

"There's a lot of people pushing HTML5 and Google has done a lot for HTML5, but the key difference is that they realise that, in terms of games, there's not really that much there yet," Hooper says. "I really don't think there's any limitations on what Native Client can do. It's still early days, but if you think about it longer term, you're running a native piece of code, so anything your PC can do Native Client should be able to figure out a way to present that to you.

"If you're thinking about delivering high-end games in a browser you've probably already realised that HTML5 isn't going to work, and now you've got this new technology option that is working. It's a game that you would normally be playing on your Xbox or PC and now it's running in a browser. It's real, it's here, and I think it's really changed the landscape even in the last 90 days [Google launched the NaCL in December 2011].

"We just didn't have that option before, but now people have seen it and that's made a big, big difference."

Both Goodale and Moore display similar admiration for what Google has achieved with NaCL, with Moore showing particular interest in the potential of the technology if it was applied to Google TV. However, Moore's doubts over NaCL are based on a fundamental belief that its longevity will depend on competing browser vendors adopting it - otherwise, NaCL could end up just another curio like Silverlight or ActiveX.

"It's not going to bread-and-butter internet," he says. "I can't imagine a time when Microsoft would take up something like NaCL, which for the time being will matter in terms of what Internet Explorer decides to do.

"But everyone will keep an eye on it, and when people see the kind of performance you can get in a browser, behind a URL, and ostensibly safe, it will keep us imagining. And if that's all it ever is that's still amazing, because it pushes the technology forward. If Mozilla decided one day that this was a good way to enable top-end scenarios it could be potentially game changing, but I'm certainly not holding my breath."

In 18 months or 2 years, the question isn't going to be, 'Can we do this in the browser?' It's going to be, 'Do we have to do it out of the browser?'

Kevin Moore, Pixel Lab

However, while NaCL may never make it beyond Chrome, that still leaves it with an addressable market of 200 million people launching the browser every 7 days, and that number is only getting bigger. For a game developer with an extensive back-catalogue programmed in C++ that's an enormous opportunity, while it also allows new developers to stick with familiar languages without drastically reducing their potential audience or being forced into a publishing contract with a console manufacturer.

Google hasn't revealed its plans for NaCL on smartphones or smart TV, but Hooper claims there is no technical reason why both couldn't happen eventually. And at GDC this year Google's game developer advocate, Colt McAnlis, announced that NaCL now runs inside Google+. Facebook has CityVille and The Sims Social; with NaCL, and the sort of companies already throwing their support behind the technology, Google+ could theoretically support head-to-head sessions of Trials HD. It's a beguiling thought

There are strengths and weaknesses to both HTML5 and Native Client. At present, the former is more a tool for the creation of consumer app and the latter is restricted to Chrome, but both indicate a strong future for the plug-in free browser as a platform for games of all kinds - casual and core, new and old.

Indeed, how quickly game developers start working with these technologies is almost a moot point, as both are being pushed forward by forces that have little to do with games: for NaCL, the rapid uptake of Google's Chrome browser and its spread across more and more devices; for HTML5, the support of many of the biggest companies on the web, all of which have a lot more riding on its future than just game development.

"I talk with a lot of big game companies, and I haven't met one yet that doesn't have some sort of HTML5 pilot work going on," says Goodale. "Everybody recognises that there's something here. Can we get to Bastion quality experiences without Native Client in the next two years, three years? We don't know, but that's where we're headed."

"It's probably just a waiting game," adds Moore. "In 1995 ordering a pizza online seemed ridiculous, but today I do it all the time - I never call a pizza place any more. It's not going to be 15 years [for HTML5]; it's going to be 18 months or 2 years, and the question isn't going to be, 'Can we do this in the browser?' It's going to be, 'Do we have to do it out of the browser?'

"I've gone from having a preference to having a strong default around web. It would have to be a very special scenario for me to go and build native. For the top of the long tail - for the top 1 per cent - will the browser be enough? No, you'll always have people writing native to get every ounce of hardware performance out. The question is: 'Where's the bar for good enough?'"

More stories

Fellow Traveller on why indies will always need digital events

Managing director Chris Wright discusses the evolution of its LudoNarraCon event, and why online pitching is here to stay

By Danielle Partis

EA won't make public statement on abortion rights

Publisher says it will only speak out when there's a “consistent perspective” shared by all staff

By James Batchelor

Latest comments (13)

Matthew Handrahan European Deputy Editor, GamesIndustry.biz10 years ago
I'd just like to draw attention to the infographic - kindly provided by Zipline Games - on the right-side of the article. It demonstrates one of the site's new functions, and I think it makes a very handsome addition to the article. Click it, and be amazed.
0Sign inorRegisterto rate and reply
Robin Clarke Producer, AppyNation Ltd10 years ago
Great in-depth analysis. HTML5 is only going to grow and improve, but it's not a panacea. The issues of tools, business model, and the practicality of adapting across different devices are hard problems that the tech press (and by extension clients and investors) are too often guilty of hand-waving away or not properly appreciating.

At this moment, hardware accelerated Flash and native smartphone apps are the sweet spot for reach, performance and monetisation. I think it's going to take considerably longer than two years for these problems to be solved for HTML5, unless someone steps in with a huge R&D budget to accelerate it (a la iOS, DirectX).
0Sign inorRegisterto rate and reply
Kingman Cheng Illustrator and Animator 10 years ago
I like the infographic. :)

It's very informative but with anything there are pros and cons, there's still a way to go with HTML 5 but I'm sure it'll get there!
0Sign inorRegisterto rate and reply
Show all comments (13)
iPhones, iPads and high-end Android phones are really good at HTML5 gaming already (social games in first place). There's still only a handful of quality HTML5 games though. As soon as the number of high-end titles grows and users get used to it all those stories about "HTML5 is not ready for games" will end. As HTML5 developer I know that there are several teams worldwide aiming to release big cross-platform social games this year. Will see them soon.
0Sign inorRegisterto rate and reply
Shawn Clapper Programmer 10 years ago
So in the infographic where is the code used for the flash comparison. Did they use bitmapdata and copypixels to animate or the years old way by moving a movieclip on an x axis, or perhaps even timeline animation?

Also, I'd *really* like to know how they did the same animation in HTML5. What's the tag for that? <animate direction="north" type="linear" addamount="5">circle</animate>

What I mean is HTML5 cannot animate! Just take your javascript and use it in ANY version of HTML silly. Or take your ANY version of HTML and call it HTML5 if you please.
0Sign inorRegisterto rate and reply
Tim Carter Designer - Writer - Producer 10 years ago
Year 1905:

Aircraft - The Good: They can fly! They can go over all forms of surface terrain.

Aircaft - The Bad: They still can't carry more than a single person and their personal effects, so they're restricted to carrying pilots, no cargo (other than maybe mail). There are very few people trained in operation and maintenance of them. Minor accidents with them can be fatal. They are...

(You get the point...)
0Sign inorRegisterto rate and reply
Dave Wolfe Game Developer, Cosmic Games10 years ago
HTML5 can animate via CSS3 transitions or using a timer in JavaScript to alter DOM elements or canvas/WebGL rendering. I don't know what method was used in that infographic, but it's at least a year out of date. JavaScript execution speed is on par with Flash now if you're using Chrome (which should be pretty embarrassing for Adobe) and other browsers are close behind. Rendering speed when both are using GPU is comparable, though I think Flash is still faster for cpu rendering, especially if vectors are involved. Adobe is finally going to start focusing more on script execution speed so I think we'll see Flash pull ahead of JavaScript again soon.

We need to develop games today, not the future. Using your aircraft analogy, lets say you wanted to travel across the ocean in 1910. Do you say "well, I predict that in 2 years air travel will be viable, so I'll wait till then." or do you just travel by boat? I don't want to wait for the current issues to be ironed out before I make my games, I'm going to use the best option available to me *now*. For some games HTML5 might be it, but for most games I would use a different technology.

As for the article, I have a few nits to pick.
"These qualities can be neatly summed up by one word: reach, and in that respect nothing else comes close to HTML5."

Flash comes close :) You can target the web, Android, BlackBerry, iOS, and Mac/Windows desktop. That covers the major platforms, but you are at the mercy of Adobe and if they don't think a platform is worth targeting (or they're simply locked out, like on WP7) then you're kinda screwed. Of course it's in their best interest to support as many platforms as possible, I don't think we'll see them dropping Android or iOS support anytime soon. Unity3d also comes close, even more so now that it can export to Flash.

I'll avoid a lengthy diatribe on why JavaScript sucks, but it sucks for doing anything complex. Yes, almost anything *can* be done in JavaScript, but code maintainability and tooling are pretty bad. I think that will become a stumbling block for HTML5 games unless you use a cross-compiler like GWT or HaXe so you can code using a less crappy language.

And lastly, nobody talked about the bandwidth problem. HTML5, NaCL, Flash, Unity3d, Java, it doesn't matter. If you want to deliver content-rich games in the browser you will have ridiculously long load times. There are some options for caching data locally, but none of them are designed to handle the large number of assets and file size necessary for games. Streaming data will be necessary, but not everything in the game can be streamed and you still have to worry about connections getting interrupted. It's even worse for mobile because you often have a slower Internet connection, less storage space, and more bandwidth restrictions. And if you're someplace with no Internet connection then you're out of luck. I just don't see that problem being overcome in the 18-24 months that Ken Moore is predicting.
0Sign inorRegisterto rate and reply
Private Industry 10 years ago
Typo it says around teh world in the infographic :)

Thats an interessting idea Tim, but there is one thing. Who knows what the future brings maybe in a year or 2 some company comes up with something way better than HTML5. It`s more like Balloon --> Zepellin --> Plane and we will see in the future if HTML5 is the plane or the Zepellin
0Sign inorRegisterto rate and reply
Jesse HR and HMI consultancy. 10 years ago
Typo it says around teh world in the infographic :)
That's far from the only typo, the whole info graphic is riddled with typos and grammatical errors, which is a shame because it's otherwise quite pleasing to the eye.

Edited 1 times. Last edit by Jesse on 24th March 2012 5:54pm

0Sign inorRegisterto rate and reply
Matt Hackett Game Developer, Lost Decade Games10 years ago
We've bet our company on HTML5 games. So far it's going really well :-) Exciting stuff is coming up in HTML5 land, that's for sure!
0Sign inorRegisterto rate and reply
Keldon Alleyne Strategic Keyboard Basher, Avasopht Development10 years ago
Okay, WebGL is the way forward regarding graphics since JS+Canvas is just too slow for pixel manipulation and there's only so much optimization that the JS compilers are capable of in real time.

For Audio we should first of all have a DirectKS / ASIO pipe for low latency audio, plus we should have a combiner type interface (or perhaps audio channels can be connected with a shader in/out type system) all with a set of standard effects in the API each using the same algorithm. This should incude the following to take the load of the commonly used effects away from JS:
- distortion, overdrive and saturation
- parametric EQ, shelving and filters
- compression and limiting
- echo/delay, reverb and the various time domain effects

That is all that is required for JS audio. My only gripe with WebGL are the minimum hardware requirements, had they been lower I'd have implemented them a long time ago. I really feel that Google made a bad decision with that and have slowed the transition towards WebGL as it really is the answer to browser gaming.

Edited 1 times. Last edit by Keldon Alleyne on 25th March 2012 11:43am

0Sign inorRegisterto rate and reply
Ben Furneaux Principal Designer 10 years ago
At Turbulenz we've got two awesome looking HTML5 games already online in beta. If anyone wants to try out the Turbulenz HTML5 games platform beta can email me at and I'll hook you up.
0Sign inorRegisterto rate and reply
Shawn Clapper Programmer 10 years ago
@Dave Wolfe
"via CSS3 transitions or using a timer in JavaScript"

Neither of those things are HTML5. Although your comment only supports my argument, I'm not sure why argue with the obvious; what this article is actually talking about and comparing; and why it seems to mention "HTML5" over and over and over with things that can be done in any version of HTML and are (like you have mentioned) not HTML.
0Sign inorRegisterto rate and reply

Sign in to contribute

Need an account? Register now.