QA Test recorders and creators have been around for a long time. The most notable one is Selenium IDE which has years and years of development. SnapTest is very similar to Selenium IDE... So why did we want to build another one?
The browser automation world is undergoing major changes, and current tooling isn't keeping up. Amazing new technologies are starting to appear that may replace Selenium entirely. A couple of the hot new ones are Cypress.io, Testcafe, Chromeless, and Puppeteer. Each one has strengths in terms of being faster, more debuggable, and less flakey. This rocks! But Selenium IDE doesn't generate code for these frameworks. There needs to be a product that does.
Selenium IDE is not in Chrome. Seems they are stuck in Firefox for whatever reason.
I want more features in a QA IDE, and I don't want to make them for a dying project Selector algorithm improvements, target fallbacks, multiple test running, integration into JIRA, etc... There are so many cool things to do with a project like Selenium IDE.
(Most important to me!) Test project generation can be for more than just prototyping: Some people are of the opinion that Selenium IDE was only good for prototyping, and I'd agree with them for the most part. But do ALL tests, even the mundane "click on this and that" tests need hand-coding? SnapTest strives to generate the mundane aspects of a QA project, but allows custom hand-crafted tests as well.