Have you looked at webstorage? Saving to notes specifically would be niche functionality and I don't think there's a way to do it.

From a user perspective, what is the benefit in them saving the score to notes?

30fps should be the baseline target for mobile devices, and there's many Android devices so you'll need to be specific.

Thanks all *relief*

beufreecasse I had very poor performance to begin with on my 820. If you upload the entire Windows Phone project to a remote location, then change the following in MainPage.xaml.cs:

private string MainUri = "/index.html";

to

private string MainUri = "http://[your remote location]/index.html";

and

Browser.Navigate(new Uri(MainUri, UriKind.Relative));

to

Browser.Navigate(new Uri(MainUri, UriKind.Absolute));

Test out this and see if the performance is better. If it is then there's a way to vastly improve performance.

Blacksmith ah this is disconcerting. We've done a lot of work on the Windows Phone version of our game but don't have a HTC 8S to test on :X

beufreecasse Can you try disabling all audio and see if that fixes it?

BluePhaze I've not had the need for an IIS server yet, but Azure Mobile Services have announced HTML support, and it looks easier to setup with IIS.

Pantaloons I've been working all today on getting it to work with the most recent builds of C2, so this will definitely make it into the new release. I think the black screen is due to a different version of jQuery being referenced in index.html.

Just updated post with the new desert world! :D

When I was researching the Pi I came across this very interesting project: Pine

ine is a project with the goal of creating an HTML5 game console that runs on Raspberry Pi. The software stack is powered by Linux, NodeJS and Chromium.

wrekr yes ;)

tipztv I have no idea whether it can be updated to release OS - I would assume so. I was getting a solid 60fps for Mortar Melon in the emulator, but I highly doubt that's anyway reflective of the hardware. We'll have to wait and see :)

tipztv I ordered the Keon as it's the lowest end device.

One of the strengths of Firefox OS is their web payment system navigator.mozPay().

dvertising has been the primary business model on the web for a long time but users have made it clear that they don?t want to see ads. Mozilla isn?t trying to directly disrupt the ad business but it is trying to fix serious privacy issues relating to ad networks.

What if users explicitly paid for content instead? navigator.mozPay() enables this kind of direct payment model: if something is good on the web, you can pay for it. It already seems to be working well for existing mobile apps. Will mobile ads even generate the same revenue for content producers as they do on desktop? I don?t have answers to these questions but one thing is for certain: the web should support businesses of all kinds and payments should be a first class feature of the web.- Source

I've heard several people say that this web payment system is one of the biggest defining factors of Firefox OS. Nobody knows what will convert more at this stage, but my inclination is that advertising may not be the way to go.