That's a great point, listening and speaking is much harder than just being able to read and match some words.
We did consider using text-to-speech to say the word out loud once you answer it, but it wouldn't be ideal to have to hear every time you wanted to unlock your phone.
Closed aperture issue should be fixed now.. (was an issue with the analytics platform going down due to traffic, not the size of images (though that is of course pretty big))
It's pretty much all CSS-based at this point. Javascript is used for tiny things like the centering of the confidence intervals.
We were looking into some of the canvas libraries out there but that really only becomes necessary when doing pie-charts and other non-rectangular shapes.
Thanks! I think I just fixed #2, I am guessing it was a Chrome/Win bug with rounded corners. Though I can't see it myself.. is the problem still there?
Well you could install it on a development site or something first. You can't currently add in a domain that's not live (since it verifies its existence by pinging)— but contact me and I can add it in manually and you could try running it locally or on a private site.
Yeah, the reason for that is that
1) if/when we add HTTPS support it will run seamlessly.
For now it just returns a blank file if included over HTTPS, and so the page will degrade gracefully (no tracking) without any security errors that would've come up from loading an http resource.
2) it's shorter.
Though you're right it does look a bit weird, I will add a note to the instructions explaining what it is and that its not a bug or anything. Replacing it with http:// would've worked perfectly fine as well.
We use the same scheme to link to the media on our CDN so the app can switch seamlessly between http and https secured sections (account,billing) without any different <head> code
Thanks. Yes it is only one page right now. I had originally planned a whole site with different sections and pages but it seemed a bit wasteful since the current integration guide is: • have jquery on your site • add a line of code linking to your JS file
But behind the scenes how it works is that JS file (ie. usecharm.com/mmelin.js or something) returns different code depending on the cookie of the visitor and the configuration of the project. So if you launch a test, the goals and changes will come out in that file and it is also based on what page it is requested from, so the change could be different when requested from the homepage of your site vs a content page. By default it just has basic analytics stuff like referrer-detection and measuring demographics.
Do you think I should add a "behind the scenes" or similar section that explains all the technical stuff going on?