[eob]

I'm happy any time I see web design/development moving into the web browser and out of text files. It feels like the natural progression of things.

Some comments:

- The example email (Weekly Summary) made me think "SPAM!" as soon as I saw it, because it looks like the kind of email that Twitter sends me and goes straight to my trash bin. On the other hand, I imagine there are a lot of use cases where summary emails are welcomed.

- Other than that, the image does a good job communicating the features you provide. I'm left wondering where the data comes from though. Do I upload a file? Integrate with my back-end?

- I was confused when the iPhone image showed template tags instead of a rendered result. Are you trying to imply that I will be editing templates using my mobile? That seems weird. If you're trying to show that your design templates are responsive, maybe just show the rendered version of the previous Weekly Summary template on an iPhone.

- Site looks slick -- I like it!

- Seeing this make me think that it would be cool for some If This Then This-style framework / API that hooks into your back-end and generates mails automatically. That would enable people to send me the emails that I enjoy reading, like "SoAndSo just cheered you on FitBit".

[gnud]

> I'm happy any time I see web design/development moving into the web browser and out of text files. It feels like the natural progression of things.

I'm often not. I'm not talking about this tool specifically (it looks very nice, and I havn't tried it), but when tools move away from text files, we tend to lose important facilities like "replace image A in all our email templates with image B".

[eob]

This is very true.

But if you buy into the "browser will become the runtime for most things" argument, you'll be able to do this within your browser-based HTML editor, too, one day.