[ignoreme]

You really should have a fallback page for browsers with no Javascript. NoScript has become increasing popular and the "Javscript Free" page of a site is the first page those users will see (even if they go on to temporarily allow javascript for your app).

In your case, it is just a blank white page. Since you are asking for suggestions, I would suggest you just make it display a message. One for suggesting users with older browsers to download chrome or firefox and another message directed at those with Javascript intentionally disabled which gives a very brief outline of what your app does and why they should enable JS to play with it.

e: I clicked through to the other mashups you have created which you linked in your other comment. They all do the same thing, just bring me to a blank page.

ee: To those down-voting, what do you disagree with? Do you not think pure JS web apps should have HTML fallback pages or do you disagree with the way I said it?

[johnnyn]

I didn't downvote you but I personally never worry about users with JavaScript disabled, and the companies I have worked for don't care either. The number of people without JavaScript is most likely way to low to spend time on an HTML fallback.

http://www.quora.com/What-percentage-of-Internet-users-use-J...

[jerf]

An adequate "fallback" is <noscript><p class='something_nice'>This site requires Javascript to function</p></noscript>. It's not exactly hard, and it's better than a blank white page.

It can also occur due to network problems on occasion or other technical issues; if you have JS beyond just progressive enhancement on your site you really ought to have a <noscript> tag in there somewhere.

[ignoreme]

It's a fair argument that overall percentage is low, but if you are catering towards a more technical audience (submitting to HN would count as that in my books) then I imagine the % of those using some form of Javascript blocking software is much higher.

Plus as mentioned, it isn't like it takes much effort, a noscript tag and a paragraph saying that it is a pure JS web app/what it does is enough.

[nl]

Do you not think pure JS web apps should have HTML fallback pages or do you disagree with the way I said it?

I don't think non-JS/HTML fallback pages are worth it for a minimal viable product.

[JonathanBouman]

Showing a 'Please activate javascript' message is indeed a good idea. A complete HTML only fallback is impossible since everything happens in the browser (JSONP API calls).