We’re switching from HelpScout to Front. We don’t anticipate a significant impact to users during the switch (though if you email the very first day we start using it, there’s always a chance of a few kinks).
Didn’t some early design mockups leak onto the forum at one point? I think they’re out there… Anyway, we plan to have a period of time where users can beta test (we’re building it in a way so that you can switch back and forth), so there’ll be an opportunity to play with it before we get rid of the old version.
Short answer is it’s very likely something we’ll eventually do, but it’s far enough out I can’t give a meaningful timeline. Likely how this will work is we’ll provide a mechanism for running multiple iterations of the app simultaneously, so that users will be interacting with the old set of workflows until they refresh the page. They’ll probably need to be some kind of time-boundedness to this, or controls for the app owner to force refreshes, so that old workflows that you want to disable eventually go away. The main technical prequisite is changes to our app storage to make it as fast to pull an older version of an app as it is to pull the current version: right now, we have the ability to roll an app back in time, but not to serve the old version in parallel with the new version.
Sorry, I didn’t mean to diminish the size of the issue – I know this is a very big deal for our European customers. I was just referring to the questions in the thread I linked to.
Mostly the former: one of the reasons we are building Bubble is because we think it’s healthy for software development to be something that anyone in the world can do, not just people with the resources to become programmers or work with programmers. But it’s not enough to just build the tool: we ned to put effort into getting into the hands of people who otherwise might be locked out of the tech ecosystem.