by bialecki on 1/3/13, 4:59 PM with 16 comments
by eob on 1/3/13, 5:26 PM
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".
by felipe on 1/3/13, 5:57 PM
Having said that, it seems that you expect the app to use your SMTP, and IMHO that's a deal-breaker. Once an app or company is already using a SMTP provider, changing to an unknown one (which could impact deliverability and so on) is a deal-breaker. However, if you provide a tool that somehow the marketing dept can change templates which then the developers can somehow fetch into the source codebase, now that would be (I think) a good value.
I am a software developer (not a designer nor marketeer) so I may not be the target user for this tool, but I think it would be valuable for developers too.
by niftylettuce on 1/3/13, 7:24 PM
by scottmotte on 1/3/13, 6:43 PM
by eli on 1/3/13, 5:42 PM
by navs on 1/3/13, 8:23 PM
by MasterScrat on 1/3/13, 9:16 PM
by dirkdk on 1/4/13, 12:29 AM
by somid3 on 1/3/13, 7:04 PM