Question about the new responsive engine

[phrase9]

Hi all

I’ve been too afraid to activate the new responsive engine due to all the issues I have seen reported. I am half way through a very complex app and my design is unconventional. I would prefer not to change and keep going as is and keep it that way forever. Is this an option or will I have to make the transition at some point and hence is me changing my design now advisable?

[mikeloc]

Check out this response from Nick in the main thread…

New Responsive Engine [beta] is Live!

Correct - we have no plans to force users off of the legacy responsive engine. Even if we did, I can’t imagine it would go over too well. That being said, our goal is to make the new engine so awesome that everyone wants to switch A big part of that “carrot” is making the migration process smoother - which sounds like is pretty poor for a number of apps. In addition to feature requests and UX tweaks, we will be looking to make this process a lot better in the coming weeks/months. …

Best…
Mike

[phrase9]

Thanks

[bcart0v]

Additionally, you can always attempt to start the transition and if you feel it’s too much work, if you click on the deploy tab and select history, you can always revert back to a specific time in history and easily revert all changes, making it very easy to go back if you feel it can’t be done.

I’ve had to use this feature a handful of times so far, especially if I’m 100 changes in on trying to make an existing page work and I realize what the issue was all along, I can simply step back in time and start fresh.

Good luck!