seilund's comments

Sebastian, the other founder of Userflow, here :)

You'll also be able to build much more advanced and in-depth flows with Userflow, not to mention checklists, launchers and surveys.

Through launching software companies in the past, I know the frustrating work of creating good screencast videos for customer support. It's practically impossible to move the mouse smoothly enough and avoid typos. When you do something wrong you have to start all over again.

With Studio1, you create a manuscript using simple text. The manuscript consists of actions such as "Go to", "Click" and "Type". When rendering the final video, Studio1 will repeat these actions, giving you a smooth video.

You can record your repeatable actions by controlling a remote browser running inside Studio1. As you click/type, your actions are automatically added to the manuscript.

For voice-over, you just enter what you want it to say, and we instantly synthesize speech using Google's Text-to-Speech API, which gives you almost-human-sounding speech immediately. That makes it easy to iterate on your wording.

We'd love feedback and questions. Cheers!

I would recommend you to take a deeper look at Ember.js.

The article above by Jesus Rodriguez is a good article. It shows how Angular is easy to create _very_ small widgets with. But it doesn't tell you much about how to write a big application.

My experience with Ember (we're creating a very large app with around 100 different routes) is extremely good. More functionality != more bulk. All new features we add to the app fit nicely with the existing code. We never have to go back and refactor large parts of the app. It's the same simple pattern you apply over and over again. I seem to get the opposite impression from Angular apps, where as soon as your app grows more complex you need to take a lot of things in a different direction.

Take a look for yourself at some big and serious companies who are building large open source Ember apps:

Discourse: https://github.com/discourse/discourse/tree/master/app/asset...

Travis CI: https://github.com/travis-ci/travis-web/tree/master/assets/s...

Balanced Payments Dashboard: https://github.com/balanced/balanced-dashboard/tree/master/a...

And check out the new getting started guides: http://emberjs.com/guides/ (especially the screencast by Tom Dale)

We are using Ember.js for our upcoming release of billysbilling.com. It's a huge app. We already have 60 different routes and several hundred .js files.

The best thing about Ember that I always tell curious newcomers is that Ember is both easy to make small apps with, but it's also trivial to keep expanding into really big apps. You can keep repeating the same pattern infinitely without rewriting old parts of the app, and without feeling like adding bulk to the app. I see our app as a large very flat structure. We can go in and replace every small piece in isolation to everything else.

My impression of something like Angular.js is that often when you want to add new features you have to go back and refactor a lot of stuff (just check out the cage match between Tom Dale and Rob Connery https://vimeo.com/68215606). It feels like a pyramid that will need a lot of maintenance to stay standing.

This is not the case with Ember. Ember was written by some very smart people, who have spent _a lot_ of time refining how an app should be developed in the long run. Features are prepared for the future. Both the future of browsers and JavaScript but also the future of developers' apps.

I am sure that Ember will prevail over all the other frameworks within the next year and stay on top for many years to come.

Ember.js is as close to being finished as it can. We have a really large app under development, using Ember.js. It works so well. Better than anything I've ever used (and I've made single page Javascript apps since way before it was cool). Development is fast and fun. Often I sit back with a feeling like "Was that all that I had to do to make this work??". The performance is good, if not great. Ember cleans up everything it creates itself, which makes it very simple to make advanced apps that are easy on browser memory consumption.

It seems like Ember Data (and documentation, which is an easy problem to solve) is currently the only achilles heel of the whole Ember. But PLEASE don't judge Ember.js based on a pre-alpha version of an add-on library. There is no sense in that. Ember Data will receive its glory once it's done. Anybody who's every implemented a data persistence layer can tell you that it's not a trivial problem to solve.

Conclusion: Ember.js IS awesome. I love it. A lot of people love it. If you don't like it, then fine. Don't hate on it for no reason. I don't like cauliflower (I hate it), but I don't hate on people who eat it. I admire that they want to be healthy.