We’re deprecating the App Editor in favor of OXIDE (updated)

Update (15 April 2021): The App Editor can no longer be used for editing apps. Please ensure that your app is migrated to be compatible with OXIDE, and use OXIDE to build and deploy your app.

After the successful launch of OXIDE in September 2020, we are deprecating the App Editor (build.journeyapps.com) and will be removing it from JourneyApps in 2021.

This notice describes the timeline for the removal of App Editor, guides you through the steps you may need to take if you are affected by the deprecation, and answers questions you may have.

What you can expect

As of 15 February 2021 JourneyApps will only provide support for critical issues in the App Editor. You will only be able to manage developer access using the Admin Portal. You will also no longer be able to create new apps in the App Editor.

As of 15 April 2021 we will be removing the capability to make and deploy changes to apps from the App Editor. After this date, the App Editor will only be able to migrate your app to be compatible with OXIDE, and cannot be used for building apps, or managing users.

No later than 1 December 2021, the App Editor will no longer be accessible.

How to migrate your app

To ensure that you can continue to make code changes to your app, you need to migrate your app to be compatible with OXIDE. To do this you a version 4 syntax app which is integrated with GitHub or our OXIDE revisions source control system:

1. Version 1 and version 3 syntax apps will need to be migrated to the version 4 syntax.

- You can do that by accessing the Version Management menu under App Settings and following the steps to migrate your app.

- There are some code changes required to ensure that the app works as intended with the version 4 syntax. Please see our guide.

2. Your apps need to be migrated to be compatible with OXIDE. Do this by going to the Admin Portal, and clicking Migrate.

Once you’ve migrated your app successfully, you can edit and deploy changes using OXIDE.

Summary of dates

1. Deprecation: 15 February 2021

2. Removing support to manage developer access: 15 February 2021

3. App editing capability removal: 15 April 2021

4. Complete removal: Latest 1 December 2021

Common questions

What happens to apps that have not been migrated by 15 April 2021?

You will no longer be able to edit or deploy your app, but it will still be accessible in the App Editor. App users will be able to use the app without any interruption, though you will not be able to deploy updates to them until the app is migrated. Please migrate your app by going to the Admin Portal, and clicking Migrate. You can find the Admin Portal by clicking on the OXIDE logo on the top left when in OXIDE

What happens to apps that have not been migrated by December 2021?

App users will no longer be able to use the app. We will place the source code of your app in cold storage. If you wish to reactivate the app and edit it in OXIDE, there will be a cost involved.

Do I need to use GitHub to be able to use OXIDE?

Your app needs to be integrated with GitHub, or use our new OXIDE-compatible JourneyApps revisions system.

What are the biggest changes for using OXIDE above the App Editor?

You can read more about OXIDE here. It is designed to be a more productive app editing IDE, saving you precious time during development, and giving you more control over your app editing environment. To get the most out of JourneyApps, you should use OXIDE.

I cannot use OXIDE by the date you have communicated. Can you extend the dates?

Unfortunately, these dates are final. Please speak to us about specific blockers that prevent you from adopting OXIDE by the above dates.

How do I deploy my OXIDE app programmatically?

We have APIs that allow you to deploy your app if it is OXIDE-compatible. Contact us for more information.