The JourneyApps Blog

Here is our latest update on new features and improvements to JourneyApps shipped in Q1 2024:

Migrate Deployments from Multi-Tenant to Single-Tenant Environments

Last year we paved the way towards a premium feature where your apps can have isolated, single-tenant backend environments. At that stage, it was possible to create new deployments in single-tenant environments. Earlier this year, we completed the necessary tooling to migrate existing deployments into these environments (including inter-regional migrations).

Migrating to a single tenant means that your app’s database will be hosted separately from other apps’ databases, providing increased data security, stability and performance. Additionally, app performance metrics can be reported for single-tenant databases, including function and query timing, database sync timing and memory usage (for Desktop platforms).

If you want to learn more about our single-tenant offering, please contact us or reach out to your account manager.

Single-Tenancy Now Supports Azure for Attachments Storage

Attachments (media such as files and images) are stored in AWS S3 in our multi-tenant environments. Since earlier this year, single-tenant environments offer attachment storage in either S3 or Azure Blob Storage.

Runtime Improvements: Better Object-Tables, Custom Icons, and More

We shipped many improvements and fixes to the JourneyApps Runtime – these are some of the highlights:

• object-tables received a lot of attention – we shipped several improvements and fixes to make these more stable and consistent with other UI components. One worth pointing out is tables’ improved responsiveness to different screen sizes.
• Added support for custom assets to be used as icons on floating action buttons and general-section items in the navigation drawer.
• View errors related to UI components are now shown on the affected component instead of in a catch-all error dialog. This allows users to proceed to interact with the view if required, and helps developers pinpoint the cause of an error.
• We released the journey.container.architecture API for Desktop platforms, which can be used to identify whether users run 32 or 64-bit containers. Lower-level details about user devices such as this are helpful for diagnosing platform-specific issues in apps and for container distribution.

Upgrade your app to the latest Runtime version to take advantage of these improvements. See the full changelog here.

Admin Portal UI/UX Updates

The Admin Portal for your organization received a number of polishes over the past month:

• In the Projects table, we now wrap project actions into a neat gear-icon button on the far-right so we can make far better use of the available space and support smaller screens.
• We introduced a Settings tab where organization owners can update the organization name. Previously, this had to be done by our support team. Additional organization-level settings will be added here over time to become self-service.
• Developers can update their names in the new User Details section in their profile (access it by clicking on your user icon in the top-right corner).

Personal Access Tokens

We shipped initial support for Personal Access Tokens (PATs), which allow developers to create auth tokens scoped to their permissions. This means that generating (and revoking) auth tokens to interact with our developer APIs (e.g. retrieving diagnostics reports and application logs) will soon be self-service. Other use cases include setting up CI/CD workflows, or creating your own CLI to, for example, manage your app deployments. Our next steps here are to integrate the PAT infrastructure with our various services, and publicly document the available APIs.

If you have an immediate need for this, please contact us and we’ll be happy to work with you directly to get you set up.

Sneak peek: View templates

We are getting close to releasing a developer preview of View Templates. These will allow developers to define UI components once, and use them in multiple views. This was one of the top-requested features, as developers often duplicate code across views or need to maintain very large view XML files. Stay tuned for a broader release announcement soon!

If you want to test the developer preview against your use case(s) once it’s ready, shoot us an email.