Hi,
we updated the new OutSystems UI - version 2.20.0, where the main impact has been on the components of the date picker and dropdown. Detail of the changes in bottom. Need to generate a new mobile version, ipa and apk? Obviously the mobile UI will be impacted but we are not sure about the need to generate a new app.
Thanks and regards
Giulia
Fixed Issues and Improvements for Outsystems UI version 2.20.0
ROU-11193- Fixed an issue where the Date Picker component generated an invalid date.This occurred when EditableInput was set to True and the Enter key was pressed in the input field.
ROU-11189 - Fixed an issue that caused the DropdownServerSide component to close when clearing the search text. This occurred when clicking the clear text icon and when on a phone device.
ROU-11183 - The logic managing Menu events now also handles screen orientation changes when the application runs on tablet devices. Previously, this logic was spread across JavaScript nodes within the App Templates so, with this update, we will need to manually remove the JavaScript nodes from the Menu OnReady and OnDestroy event handlers and pass the callback to the new client action called MenuReady.The code remains retro-compatible, and a deprecation warning will be logged in the console. However, we recommend making these changes to reduce technical debt and ensure future compatibility.
ROU-11179 / RPM-5212 - Fixed an issue where the DatePicker component displayed an incorrect InitialDate.This occurred when used to display dates from specific time zones (e.g., Pacific Time).
ROU-11113 / RPM-5191 / RPM-5219 - Fixed an issue that caused the DatePicker and DatePickerRange components to have two inputs visible.This occurred when DatePicker or DatePickerRange components were used inside an InputWithIcon component.
ROU-11053 - Created two new client actions called MenuReady and MenuDestroy client actions to properly manage accessibility behaviors on the Menu block. For previously created applications, you can get the dependency for these client actions and apply them to the Menu block.
ROU-11042 - Fixed an issue that caused the ButtonGroup validation message to appear in the wrong position.This occurred when using the ButtonGroup inside a Form and with Mandatory set to True.
ROU-11023 / RPM-5172 - Fixed an issue that caused the DatePicker and DatePickerRange components not to properly update the year when navigating using the keyboard.This occurred when a user pressed Enter after focusing on the month selector.
ROU-11016 / RPM-5169 / RPM-5177 - Fixed an issue that prevented MenuIcon from receiving the focus and triggering the associated action when navigating with the keyboard.This issue occurred when using the Tab key to reach the MenuIcon on phone or tablet-sized displays, and pressing Enter or Space did not activate the Menu Icon as expected and, the focusable elements inside the Side Menu weren't properly updated once the menu got closed.
ROU-11005 - Fixed an issue that caused the DatePicker, DatePickerRange, MonthPicker, and TimePicker components to still receive focus when their input fields were disabled. This occurred due to a missing validation check for the disabled status.
ROU-10988 - Fixed an issue that caused the DropdownSearch/Tags accessibility not to work properly after closing.This occurred when the DropdownSearch/Tags components were closed by pressing the ESC or Tab keys.
You need a new app build when you change one of the following:
So just using a new version of Outsystems UI should not require a new app build.
Regards,
Daniel
Thanks, so - I understood that we don't need to regenerate a new app version.
Correct if non of the conditions I mention apply for your change.
When you update the OutSystems UI in your existing mobile application, whether you need to generate a completely new mobile app depends on the nature of the changes you've made. Here’s a breakdown to guide you:
1. Minor UI Updates:
If your update involves minor changes to the OutSystems UI, such as adjusting button styles, colors, or layout tweaks, you likely do not need to generate a new mobile application. OutSystems is designed to handle UI changes dynamically, and many changes can be reflected on mobile applications without requiring a full rebuild.
2. Significant UI Overhaul:
For more significant changes, such as major redesigns, new pages, or major alterations in the user interface components, you may need to rebuild the mobile app.
3. Mobile App Updates in OutSystems:
In OutSystems, when you make updates to the UI and then publish them, the platform provides automatic handling of updates on the server-side. However, for mobile apps (iOS and Android), new versions need to be packaged and distributed.
4. Testing & Compatibility:
After implementing UI changes, it's essential to conduct thorough testing on both iOS and Android devices to ensure that the new UI elements work as expected and do not affect the app’s performance.
5. No Need for Full Redesign:
In contrast to traditional website development projects where a full redesign might be necessary, platforms like OutSystems enable faster updates to your mobile applications. If you're using a WordPress-based website or progressive web app (PWA) along with your OutSystems app, those updates can often be reflected more seamlessly without needing to regenerate the entire application, as the UI changes are more flexible in these environments.
If you are also working with WordPress development or customized website development, keep in mind that UI/UX updates on the web platform (like WordPress) can often be rolled out without requiring a full app re-deployment, but this depends on your app’s integration strategy.
If you're facing challenges or need assistance with generating mobile app updates after UI changes in OutSystems, feel free to reach out. We specialize in custom website and app development, including WordPress solutions and mobile app development, and can help ensure your app stays up-to-date and fully functional.https://budventure.technology/