Creating a New App
Ensure you are in the Apps tab and click the Create App button.
Enter your app's name and select a region. Your app will be created with a testing deployment, and the region specifies in which geographical region the deployment's data will be stored. Note that for each additional deployment you create in OXIDE you can specify its respective region.
Next, select your preferred version control for your app.
JourneyApps provides a choice between Basic (Revisions) and Advanced (Git) source control options.
- The Basic (Revisions) option is suitable for smaller apps with only one or two developers, where simple restore points for your code are sufficient. This option requires zero configuration from the developer and therefore is the most convenient option to manage smaller codebases.
- The Advanced (Git) option is recommended for larger, more complex apps where a team of developers is involved - since this option will allow developers to work on different branches in OXIDE. When combined with a git provider such as GitHub (see next section), you can follow your existing DevOps practices and fully utilize git best practices.
Additionally, you can choose between JourneyApps and external providers such as GitHub and Azure Repos (currently in Beta) as your git provider. This dictates where your code repository is hosted.
- The JourneyApps option means we host your repository. This option requires no additional configuration.
- The GitHub and Azure Repos options allow you to host your app's code in your GitHub organization or Azure DevOps project respectively. This means you have access to you app's codebase outside of OXIDE. Combined with the Advanced (Git) source control option, developers will be complete work using git best practices, including code reviews and methodologies like trunk-based development or git flow. With these external git providers, developers can also enforce security best practices on their application code using functionality such as branch protection to ensure that only authorized changes are deployed to production apps.
For further details about git-enabled apps and their setup, see this page:
Finally, choose a template for your app:
The Template option allows you to choose from previously published apps, that solve use cases in specific industries or contexts. For example, here you can choose a "Warehouse Fulfillment" template - which provides some skeleton code and basic UI for typical warehouse fulfillment use cases.
The Clone an existing app option allows you to clone any other app in the organization. Select this option if you want to reuse the majority of code and UI from an existing app.