New Email Designer

Hi ​@bjohnson-5, Please check this out if it seems helpful.

Hi ​@bjohnson-5 ,

This is definitely a major pain point for lot of Marketer’s currently.

Email editor 2.0 is available for more than 9 years now & many of the business have deep email strategies spined around it.

Having said that New Email editor is also designed & built for scale & with the new capacity of migrating your email 2.0 templates to New email editor give you a additional layer of confidence.

But YES still full migration to new email editor will be cumbersome & time consuming.

I will recommend you to start using New email editor by building your new email campaigns. Start with creating new email designs which will give your clients new prospective to your communication & also provide your team with opportunities to have a hands on with the new tool, before initiating the more complex task of migrating your old templates into new editor.

Also by that time new editor will also become more stable & more features will be added by the passing time.

Hope this Helps 🙂 

We work with lots of clients across various industries and from what I’ve seen folks are still kinda where you’re at -- still testing it out and discovering the bugs and issues that keep it from a state of true parity with the Email 2.0 system and are reluctant to actually make the switch.

I’m a front end developer with a decade of experience in Design Studio and I’ve been recommending to our clients to wait until the new tool is fully cooked. There’s still a lot of updates going on and some of them have been breaking updates that force you to delete and redo things that you’ve already done b/c the updates aren’t seamlessly integrated with the previous iteration. This is a huge issue for any team that wants to get up and running and not accrue technical debt to go back and fix things which have already been QA’d -- it’s one step forward and two steps back for now from my point of view.

There’s also some serious underlying codebase issues with the Acrite editor which is the drag-and-drop foundation of this new editor. Maybe someday the codebase issues will be addressed and things like background images in Outlook will actually work, but for now it seems the engineering team is adding bells and whistles rather than addressing the underlying issues and existing issues like fragments, disjointed UX and a poor “what you see is what you get” experience. From a technical perspective, the way that edits are implemented when you click a button in the new editor is a long way from industry-standard and best practice methods for “doing a thing” and if you run some render tests you’ll quickly discover that the way the code from the editor is implemented is not supported across industry-standard email inbox services.

I’ve also tried the template import tools and things that are supposed to make it easy to migrate from EM 2.0 to the new editor and they’re still very lacking. It “sounds like” you can just grab a template and import it into the new editor but the reality is that it would be less work to start from scratch compared to going back in and editing the issue that arise from the import. Note also, that this is a lot like using AI to code things -- there’s the risk of using code that’s not vetted at a professional standard and that can be a costly gotcha’ which needs to be worked out by a good developer at the end of the day -- said another way, the “you don’t need a developer” pitch is a myth … and from a developer’s standpoint, it’s much easier to produce working code in the first place than to troubleshoot and fix something that a machine wrote. This’ll cost you more in the long run than getting it right in the first place, and in some cases because of how locked down the backend of the new editor is, these fixes aren’t possible by comparison to the Email 2.0 system where the code base is opened up.

There’s a similar post in the community here for additional consideration: 

​@Dave_Roberts - I completely agree. We had developers make all of our templates back in 2022 and I’ve been using them ever since. I’ve managed to code some modules myself with the help of AI.

In regards to the new editor, with every “update” I’ve tried it again and I simply can’t commit to it. Like you, I tried to import a 2.0 template and it didn’t even bring over the functionality to make it mobile. Then my rep tells me there’s a completely new editor coming soon. I followed up with a “will this new editor actually work?” and he laughed but understood my frustration because of all the reasons you listed above.

I’ll continue keeping on using my current templates for the timebeing. Thank you for your response!

Hey ​@bjohnson-5 what did your rep mean when they said there’s a completely new editor coming soon? Is that to replace the current new editor? I’ve just ported our new template over and the new editor is giving some serious headaches!!