Comments on: Inside the MailChimp Interface Design Process http://blog.mailchimp.com/inside-the-mailchimp-interface-design-process/ MailChimp, email marketing, and monkeys! Thu, 09 Feb 2012 21:21:24 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: 4 Work Apps with Awesome UX and UIhttp://blog.mailchimp.com/inside-the-mailchimp-interface-design-process/#comment-36529 4 Work Apps with Awesome UX and UI Thu, 27 Oct 2011 16:53:30 +0000 http://blog.mailchimp.com/?p=3279#comment-36529 [...] MailChimp’s employees consider UX to be critical and talk about this at length on their blog. SparrowIn user experience and design, the Sparrow app is an e-mail app meant to keep things [...] [...] MailChimp’s employees consider UX to be critical and talk about this at length on their blog. SparrowIn user experience and design, the Sparrow app is an e-mail app meant to keep things [...]

]]> By: Outsourcing Projectshttp://blog.mailchimp.com/inside-the-mailchimp-interface-design-process/#comment-8209 Outsourcing Projects Wed, 19 May 2010 11:10:27 +0000 http://blog.mailchimp.com/?p=3279#comment-8209 I see. Yup, right now you can’t do that on the unsub page, but we might add that feature in a future version. Thanks for that feedback. --------------------------------- sujatha I see. Yup, right now you can’t do that on the unsub page, but we might add that feature in a future version. Thanks for that feedback.
———————————
sujatha

]]> By: Outsourcing Projectshttp://blog.mailchimp.com/inside-the-mailchimp-interface-design-process/#comment-8208 Outsourcing Projects Wed, 19 May 2010 11:09:57 +0000 http://blog.mailchimp.com/?p=3279#comment-8208 I see. Yup, right now you can’t do that on the unsub page, but we might add that feature in a future version. I see. Yup, right now you can’t do that on the unsub page, but we might add that feature in a future version.

]]> By: Outsourcing Projectshttp://blog.mailchimp.com/inside-the-mailchimp-interface-design-process/#comment-8207 Outsourcing Projects Wed, 19 May 2010 11:09:10 +0000 http://blog.mailchimp.com/?p=3279#comment-8207 Iam a new user of Mailchimp and really appreciate your good work! Suggestion: in “Form Design” page, the user interface implies one can build and design each of the different forms. In fact, it only applies to the Subscribe Page. The left blue box called “forms & response emails” has a drop-down menu below it and arrow to the right. Makes user feel one needs only to choose the form, and then design it. I’d love that! Thanks. Iam a new user of Mailchimp and really appreciate your good work! Suggestion: in “Form Design” page, the user interface implies one can build and design each of the different forms. In fact, it only applies to the Subscribe Page. The left blue box called “forms & response emails” has a drop-down menu below it and arrow to the right. Makes user feel one needs only to choose the form, and then design it. I’d love that! Thanks.

]]> By: mrdatahttp://blog.mailchimp.com/inside-the-mailchimp-interface-design-process/#comment-4209 mrdata Thu, 02 Jul 2009 16:26:41 +0000 http://blog.mailchimp.com/?p=3279#comment-4209 what's the difference between designing prototypes using HTML or Photoshop?It's a fact that using HTML you save time on coding hours, but, don't you have to get back to Photoshop to design shapes and colors? what’s the difference between designing prototypes using HTML or Photoshop?

It’s a fact that using HTML you save time on coding hours, but, don’t you have to get back to Photoshop to design shapes and colors?

]]> By: Aarron Walterhttp://blog.mailchimp.com/inside-the-mailchimp-interface-design-process/#comment-3924 Aarron Walter Fri, 22 May 2009 18:01:29 +0000 http://blog.mailchimp.com/?p=3279#comment-3924 I see. Yup, right now you can't do that on the unsub page, but we might add that feature in a future version. Thanks for that feedback.You are right that the interface is actually misleading in that spot. Either way, we'll do our best to clarify and improve. I see. Yup, right now you can’t do that on the unsub page, but we might add that feature in a future version. Thanks for that feedback.

You are right that the interface is actually misleading in that spot. Either way, we’ll do our best to clarify and improve.

]]> By: Nancyhttp://blog.mailchimp.com/inside-the-mailchimp-interface-design-process/#comment-3920 Nancy Fri, 22 May 2009 16:40:02 +0000 http://blog.mailchimp.com/?p=3279#comment-3920 Hi Aarron - thanks for your reply. When I try to add a multiple choice, mini-survey on our UNSUBSCRIBE page, it places "radio buttons" etc. on the SUBSCRIBE page. I went to Live Support and Raul confirmed for me that one cannot add these design features on anything but the SUBSCR page. Please advise. Thanks! Hi Aarron – thanks for your reply. When I try to add a multiple choice, mini-survey on our UNSUBSCRIBE page, it places “radio buttons” etc. on the SUBSCRIBE page. I went to Live Support and Raul confirmed for me that one cannot add these design features on anything but the SUBSCR page. Please advise. Thanks!

]]> By: Aarron Walterhttp://blog.mailchimp.com/inside-the-mailchimp-interface-design-process/#comment-3916 Aarron Walter Fri, 22 May 2009 12:46:25 +0000 http://blog.mailchimp.com/?p=3279#comment-3916 @Nancy - thanks for the feedback. Maybe I'm misunderstanding your suggestion, but that is in fact the way the interface works. Could you clarify? @Nancy – thanks for the feedback. Maybe I’m misunderstanding your suggestion, but that is in fact the way the interface works. Could you clarify?

]]> By: Nancyhttp://blog.mailchimp.com/inside-the-mailchimp-interface-design-process/#comment-3913 Nancy Thu, 21 May 2009 19:32:23 +0000 http://blog.mailchimp.com/?p=3279#comment-3913 I am a new user of Mailchimp and really appreciate your good work! Suggestion: in "Form Design" page, the user interface implies one can build and design each of the different forms. In fact, it only applies to the Subscribe Page. The left blue box called "forms & response emails" has a drop-down menu below it and arrow to the right. Makes user feel one needs only to choose the form, and then design it. I'd love that! Thanks. I am a new user of Mailchimp and really appreciate your good work! Suggestion: in “Form Design” page, the user interface implies one can build and design each of the different forms. In fact, it only applies to the Subscribe Page. The left blue box called “forms & response emails” has a drop-down menu below it and arrow to the right. Makes user feel one needs only to choose the form, and then design it. I’d love that! Thanks.

]]> By: Chadhttp://blog.mailchimp.com/inside-the-mailchimp-interface-design-process/#comment-3858 Chad Thu, 14 May 2009 10:38:41 +0000 http://blog.mailchimp.com/?p=3279#comment-3858 To add to Aarron's comment, the primary benefit of using Mercurial over SVN/CVS is that is adds tons of flexibility in how our developers branch and reintegrate new features into the codebase. It also does much better with merging over changes without conflict during releases. We also fell in love with BitBucket for hosting the master repository with an excellent interface. Git will behave almost exactly the same, but I found Mercurial's language and approach slightly easier to understand and use.However, decentralized version control has a couple of issues. The team will tend to hold back changes longer, committing in bigger chunks. This is a good thing for keeping the repository clean and working, but bad if you've got somebody that commits locally but never pushes to the master. Also, because there's no centralized timeline of commits, each developer will increasingly need to merge changes together as a part of normal development, filling the commit log with empty merge commits.Hope this helps. To add to Aarron’s comment, the primary benefit of using Mercurial over SVN/CVS is that is adds tons of flexibility in how our developers branch and reintegrate new features into the codebase. It also does much better with merging over changes without conflict during releases. We also fell in love with BitBucket for hosting the master repository with an excellent interface. Git will behave almost exactly the same, but I found Mercurial’s language and approach slightly easier to understand and use.

However, decentralized version control has a couple of issues. The team will tend to hold back changes longer, committing in bigger chunks. This is a good thing for keeping the repository clean and working, but bad if you’ve got somebody that commits locally but never pushes to the master. Also, because there’s no centralized timeline of commits, each developer will increasingly need to merge changes together as a part of normal development, filling the commit log with empty merge commits.

Hope this helps.

]]>