https://freeroam.app (has BLM overlays)
818 karma · joined March 6, 2012
Thanks for pointing out the screen resolution and browser history things.
It started out as a js1k entry (https://github.com/Zolmeister/Zop/blob/35a428661320ba9ad8e5e...)
It's a tough situation to be in where they need to improve the quality of the ecosystem, but need users to convince the big-wig devs to developer for the OS. The total user numbers we've seen from them is certainly better than we expected, but still too small to convince a major developer to build for Firefox OS on numbers alone.
If their platform wasn't the web, I'm not sure they'd have much of a chance at success, but being able to convince a developer the values of building for the web is much easier than building for a fairly new mobile OS.
===================
What we're building
===================
==============
Where we're at
==============
See http://stackshare.io/clay-io/clay-io for our stack and to get a better feel for the code we write see https://github.com/claydotio/clay-mobile
=========
Our Stack
=========
Hiring Full-Stack Engineers. Shoot me an email: austin@clay.io
===================
What we're building
===================
==============
Where we're at
==============
=========
Our Stack
=========
Hiring Full-Stack Engineers. Shoot me an email: austin@clay.io
===================
What we're building
===================
==============
Where we're at
==============
=========
Our Stack
=========
Hiring Full-Stack Engineers. Shoot me an email: austin@clay.io
===================
What we're building
===================
The approach we're taking focuses on mobile web games - games people can access immediately without the added friction of installing them in an app store.
==============
Where we're at
==============
=========
Our Stack
=========
Hiring Full-Stack Engineers. Shoot me an email: austin@clay.io
===================
What we're building
===================
The approach we're taking focuses on mobile web games - games people can access immediately without the added friction of installing them in an app store.
==============
Where we're at
==============
=========
Our Stack
=========
Hiring Full-Stack Engineers. Shoot me an email: austin@clay.io
===================
What we're building
===================
The approach we're taking focuses on mobile web games - games people can access immediately without the added friction of installing them in an app store.
==============
Where we're at
==============
=========
Our Stack
=========
Shoot me an email: austin@clay.io
About Us -------- We're redefining gaming on mobile. The primary means of discovery for games is through the app stores, which we think is a bad approach... There should be a Steam equivalent on mobile and that's what we're working on. We're already reaching 4 million people every month and just getting started.
We're a small team with a huge passion for games. We're all technical and big fans of open source, so a good chunk of what you write will be public on GitHub.
Our Stack --------- Node.js, CoffeeScript, MySQL, MongoDB, HTML5, Ansible, Docker, Gulp, ...
People are using apps instead of the web for certain services because they're easier to find (both initially, and for subsequent uses), easier to use, and more polished. The point is, this is all changing in favor of mobile web. Mobile apps can become just as easy to use and have close to the same level of polish, but more importantly, they can become easier to discover. Flappy Bird was successful because of social media, not discovery directly from the app store - the app store just added more friction.
Retention is the biggest potential point of failure for mobile web, and that's something I think Kik has solved pretty well. There are other examples of good solutions for this (eg Firefox OS), but none of them have enough traction to serve as a good proof-point.
It's interesting to see how the indie scene and game devs in general react to something like Flappy Bird.
A lot of these unfortunately don't work on mobile devices :/ I'm working to try and get more folks serious about developing for the mobile web - but it is a much more difficult task than developing for desktop-only.
The point I was trying to make is Bombermine is somewhat of a mix between a website and a game, and it works well for it.
For example, the Tizen App Challenge (https://developer.tizen.org/contests/tizen-app-challenge) is offering some pretty large prizes for HTML5 apps/games.
It was pretty straight-forward to implement and has a nifty backend to it as well for managing the algorithms.
He won last year with http://spacepi.clay.io
However, to answer your question, we take a 20% cut on any transactions made through selling games or our in-game payments API. If you're using our Advertising API we take 10-30% (depending on where the game is being played). Everything else (leaderboards, achievements, etc...) is free to use. This info is displayed here: http://clay.io/docs
What needs some work is making those games stickier in the sense that the person will play it again. That requires saving it to the home screen which probably not enough people are familiar with - and is a bit of a pain on Android.
I like the approach Firefox OS has taken with saving/installing apps and hopefully Apple and Google follow suit. As is, I think iOS's "Add to Home Screen" is fine. Android's like I said, could be improved.
The other thing that needs a bit of work is HTML5 performance in the webview. On iOS at least, game's don't perform as well as when they are played in Safari (since the webview doesn't use the Nitro JS engine) - hopefully that changes soon.