The Death of an HTML5 Game Breeds an Open Source Project

colinneagle writes "German social gaming company Wooga has thrown in the towel on its HTML5 project after seeing little return on the increasing amount of effort put into its Magic Land Island game. Some early success convinced Wooga to devote additional resources to the game, which was launched in October of last year. However, 'As the project continued to progress, so did the industry. Whilst the benefits of an open platform future are clear for games developers, it became clear halfway through Magic Land Island's development cycle that the technology wasn't yet ready for mainstream exposure.' The announcement sheds some interesting light on HTML5, as Wooga hardly holds back on any of the details behind the game's failure. The biggest barriers to HTML5's entry to the mainstream include internet connectivity and limitations on sound. The consensus? The time for HTML5 will come; it's just not quite there yet. In the meantime, Wooga has made the game open source so other HTML5 developers can learn from it."

Comments

Please, no sound

[Hatta]

Sound in web pages has been an abomination since the moment it was introduced. I never want to have to go searching through dozens of tabs looking for the one website that thinks its so important that it needs to blare audio at me. Anything that plays audio without the explicit consent of the user is incredibly impolite.

Compile, make packages, offer download

[tepples]

You can't run C++ from a browser using any sort of standards

You can if you code to SDL (the de facto standard for 2D games' I/O), compile it for Windows, Mac, X11/Linux, and Android, and then offer binary packages (msi, dmg, deb/tgz, apk) through standard HTTPS. The only browsers you won't hit with this method are Safari for iOS, IE for Windows Phone 7, IE for Windows RT, and browsers for game consoles.

Re:Compile, make packages, offer download

[kripkenstein]

You can compile C++ to JS and run it on the web, using Emscripten. It supports SDL.

Here is an example 2D game ported that way: http://www.syntensity.com/static/mams/mams.html

Re:But Flash is dead, right?

[gaspyy]

I hate to break it to you but many apps in the AppStore, including award-winning ones are built in Flash and packaged as apps.

The whole crusade against flash is just the new generation rebelling the old one, not completely unlike the nosql movement.

Media capture API

[tepples]

Flash is dead, yes. It didn't run on all devices like HTML does

Flash's media capture API runs on a lot more devices than HTML5's. So do Flash vector animations, without having to bloat them by a factor of ten by rendering them to cosine-transform-based video.

Using apps ensures literally 100% compatibility with the target device

And 100% more headaches with the device manufacturer's screening process, as the article points out.

Re:But Flash is dead, right?

[Anonymous Coward]

You can't run C++ from a browser

That's the point. You shouldn't be making game and programs meant to run in a web browser.

Re:No autoplay on YouTube?

[Metabolife]

When you go to youtube, you're asking for video. When you search the web for information on bananas, you're not asking for "I'm a banana" repeating in the background as you read up on the cultivation and export of the fruit.

They can, but only for hand-picked devs

[tepples]

Technically C++ runs on those devices, but the ability to execute native code is cryptographically locked down so that only a few developers selected by Microsoft can code in C++. Everyone else has to use C# or another statically typed, verifiably type-safe CLR language. DLR languages such as IronPython require Emit, which is not present in the .NET Compact Framework, and P/Invoke raises a security exception.

Re:I'd settle for

[Calydor]

No, he's absolutely right.

D3 is nothing more than D2. It is, however, a lot less.

Re:But Flash is dead, right?

[drkstr1]

I hate to break it to you but many apps in the AppStore, including award-winning ones are built in Flash and packaged as apps.

And the ones that don't suck aren't.

We have a Flex AIR app that compiles to iOS and Android (plus all the other usual suspects). It runs better than _any_ of our competitor's, especially the ones based on HTML5. Oh, and the HTML5 based apps look like crap, in addition to running like it.

Now I realize that coding in pure native has the potential to be faster, but in practice, your developer is the limiting reagent. We greatly benefit from the cross platform capabilities and rapid development (scale-9 slicing + solid vector graphic framework+ countless other things I have been spoiled with over the years), and all without any noticeable degradation in performance.

I hope more people are as closed minded as you, because that means more money for me.