We're considering Outsystems as a platform on which to migrate our digital ecosystem for electronic health records, inventory, time and attendance, HR, fleet, asset management, contracts, etc.
Ideally, we would choose a native mobile app development built on React Native and not Cordova. PWA - Interesting concept and useful complement to a native app, but the higher battery drain and less snappy performance would be difficult for our users relying on the system all day in the field
Reactive Web - Useful to build to modern stack but doesn't support off-line content or have as much hardware integrationNative App - We're most interested in this route but dislike building on Cordova instead of React Native. If we built a new native app now that currently uses Cordova framework, we wouldn't want to rebuild the solution again for React Native.
I think there is no clear timeline for this.I am hoping they'll give us a solution to easily port over applications
Hi Sam,Please check how does OutSystems support mobile development.
OutSystems Reactive Web app is indeed not suitable option to deliver a mobile app. You need to create a Mobile app and deliver as a PWA or install and run on iOS and Android devices, and they adapt to different form-factors using a single code base. OutSystems achieves this by generating highly performant hybrid applications that use the Cordova framework.
Native mobile apps have definitely a few strong pros, I take this opportunity to share a few articles that may help to deconstruct the pros of native apps/arguments:
In my humble opinion, native is only the answer if any other option/technology is preventing you to achieve your goals/requirements.I have not seen many users getting away from OutSystems just because of the Hybrid approach, as example we have several existing customers that have excellent ratings you can see for yourself in the respective app store rating:
I can share more examples if needed.
As Eric mentioned, there is no timeline for OutSystems to change the way how the mobile (hybrid) apps are being delivered with OutSystems, but even if we change the underlying stack, OutSystems uses several strategies to mitigate the impact of retiring, replacing, or deprecating features, you most likely won’t be affected
Hi Sam,
We are aware of the fact that using Cordova may cause some friction in specific uses cases. But like Daniel said, using hybrid technologies with the OutSystems ecosystems, you can mitigate almost all gaps.
Nevertheless, OutSystem's mobile value proposition is to provide a state-of-the-art mobile builder, and because of that we are actively working to fill any gap that our solution may has.
We will let you and all community know more news, as soon we have news to share.
Thank you.