To clarify the responsive engine plan:
- We have no plans to force apps that are currently on the old engine to move to the new engine: we are very aware of how much work that would be! We can’t commit to supporting the old engine forever, but, if hypothetically we were to decide to remove the old engine some day, we would a) give the community plenty of advanced warning (ie, likely on the order of a year or so), and b) we’d likely only consider initiating a deprecation process after the vast majority of apps had voluntarily switched over. So, no need to worry about being forced into an extremely expensive migration on short notice.
- That said, we do plan to stop investing in the old engine: we’ll fix anything we inadvertently break, but we aren’t going to be adding new features or fixing long-standing issues. Once the new engine is out of beta, we plan to remove the option to create new blank apps using the old engine.
In other words: if you’ve already invested a lot of time into an app on the old engine, you’re going to be okay – we’re not going to pull the rug out from under you. But, we do see the new engine as the future of Bubble, and once the new engine is out of beta, we will strongly encourage that insofar as you’re starting from a blank slate, either with a new app or a new page, that you use the new engine.