As always we have been hard at work to bring JourneyApps developers more power and flexibility, without sacrificing speed and reliability.
All Pricing Plans Now Have Unlimited Developers 🚀
Remote work is more important than ever. To unleash the potential of collaboration in your organization, we’re now allowing unlimited developers on all JourneyApps pricing plans.
You can add as many developers in your organization as you need, and collaborate using git workflows and live co-editing in OXIDE.
If you are still considering JourneyApps, you can start with the platform for Free today — and see how you and your team can build apps together more effectively.
Introducing Our New Sync Indicator
PowerSync is one of the key features of JourneyApps, which helps to keep app users fully productive, whether they are online or offline. Based on your feedback on our Public Roadmap, we have made a host of usability updates so that app users can better understand their connectivity and data sync status.
Here are some of the specific improvements users can expect:
- It is clearer for app users whether they are downloading and uploading data, uploading attachments, or downloading app updates.
- Users will see a progress bar, which indicates how much data still needs to be uploaded or downloaded.
- If users lose connectivity or there are other sync-related errors, we show that in an intuitive way.
The new sync indicator is available as part of v4.76 of the JourneyApps Runtime, which is currently in RC.
Avoid Data Wrangling Workarounds with Queries by ID
We have updated the JourneyApps Runtime and CloudCode to allow queries using object IDs. Previously, if you wanted to display a list of users or other objects excluding the currently active one, it would require onerous workarounds using data arrays.
With the new update, you can simply do a query like this:
DB.my_object.where("id != ?", some_object.id), which filters out
some_object from the query.
Querying by ID is available in CloudCode v1.9.8 and JourneyApps Runtime v4.76 (RC).
Developers can now call
journey.leaveApp() from the app’s JS, which logs out users and forces them to sign in before accessing the app again. You will find this useful in cases where users share a device, and it’s important to ensure that the correct user is logged in when performing their work. Read up about it here.
OXIDE: Get the Most Out of Tabs with View XML/JS Linking
I’d like to share a recent addition to OXIDE — the ability to link related tabs.
In Advanced IDE mode, you can open many views in parallel, and the code is displayed side-by-side in tabs. Developers can then select tabs individually, to individually edit specific XML or JS files. Alternatively, you could select the view using the sidebar on the left, to open the related XML and JS side-by-side again.
We’ve now added the ability to link view tabs, so that when you select a specific view JS tab, the corresponding view XML tab is also brought to focus.
This saves time, allowing you to get the best out of editing views with tabs while still giving you the flexibility of using tabs the way you prefer.
That’s it for now. I look forward to sharing more updates with you soon!
Make sure you don’t miss any JourneyApps product updates by subscribing to the JourneyApps Product Newsletter here.