As always, we have been hard at work shipping new features on JourneyApps. Here’s the latest:
Your App, Your Style
We’re excited to announce that we’ve added greater customization of the look and feel of your apps!
You can define themes for an entire app, and extend or customize those themes to work uniquely on specific views. Individual UI components can also be styled according to one of your predefined themes. Themes include options for customizing colors, sizing, and also component attribute options (for example, whether all
object-table components in your app should have
controls enabled or not). Have a look at the documentation to learn more.
TypeScript App Packages
App packages provide a way to write and maintain reusable code throughout TypeScript apps. They are particularly useful for projects that require custom build commands, such as webpack.
A core use case for app packages is HTML bridge projects. Previously, developers could only bind and maintain a single HTML source file to an
<html/> component within OXIDE (by uploading the HTML file as an asset). With app packages, you can now maintain large custom HTML projects in OXIDE very easily, thereby improving developer productivity.
For an overview of app packages, see the documentation. Below, we’re showcasing two prominent use cases for app packages:
Use Case Spotlight: In-app PDFs incl. CLI
App packages allow you to dynamically generate and display PDFs within an app. A major benefit is that these PDFs can be generated while the device is offline. You can also store and maintain all files needed to render the PDF in OXIDE. We’ve included a template for easily creating such app-generated PDFs in OXIDE.
Read our guide for this use case here.
Use Case Spotlight: App Unit Testing
App packages provide an easy way to create a reusable library that is also fully tested — all within OXIDE. You can use industry-standard testing frameworks such as Jest to test specific critical functions or calculations that your app relies on.
Read our guide through this use case here.
Testing Deployments and Git Improvements
We’ve listened to your feedback, and released a few exciting features related to testing deployments!
First off, you can now create new “long-lived” testing deployments. Secondly, you can choose to use such a testing deployment when you deploy to the testing environment, no matter which git branch you may be working on.
As a bonus, if you wish to deploy to a specific deployment from a specific branch, you can also set up OXIDE to do that. Finally, we will no longer create new “branch-linked” deployments when you create a new git branch.
Combined, these new updates allow you to better use git workflows. Each developer in your team can set up a long-lived testing deployment, seed it with the relevant testing data, and use that for development.
You can then create feature or hotfix git branches without having to duplicate your data setup. You could also create a shared testing deployment with representative data volumes for testing performance, sync rules, or more!
Read more about configuring testing deployments in OXIDE here.
That is it for this update, look out for more updates soon.