Announcing the discontinuation of the OutSystems Now App

Hello,


This month – July 2020 – we'll release Progressive Web Apps (PWAs) for everyone. In case you haven't heard about them yet, they're new mobile-optimized versions of web apps that you can install through your browser. They increase customer adoption and retention by engaging customers with frictionless experiences.


With PWAs, you'll also be able to test the look and feel of your native apps without having to generate a native build. With this new and improved testing capability enabled by PWAs, we will discontinue our existing OutSystems Now feature.


From Platform Server 11.9 onwards, the OutSystems Now experience will no longer be available in the development environment experience. OutSystems Now will still be available in Google Play and TestFlight until November 2020. After that date, we'll also remove it from Android and Apple stores.


OutSystems Now stopped being supported earlier this year, and we advise our customers to move to PWA mobile testing as soon as possible.


Update: OutSystems Now will stop being available on January 4th 2021


Thanks,

The OutSystems team

Hello Hugo.


How can we test/see mobile apps in IOS and Android after November 2020 ?

Thanks

Eurico Matias wrote:

Hello Hugo.


How can we test/see mobile apps in IOS and Android after November 2020 ?

Thanks

"With PWAs, you'll also be able to test the look and feel of your native apps without having to generate a native build. With this new and improved testing capability enabled by PWAs,"

 

Eurico Matias wrote:

Hello Hugo.


How can we test/see mobile apps in IOS and Android after November 2020 ?

Thanks

 Hi Eurico,

You can use PWAs to test and view your mobile apps after that date.

Thanks,
Hugo Gonçalves

 

Thanks guys, I think it will be important to share in this post some link to a page with information on how to use PWA in tests.

Cheers

Miguel Verdasca wrote:

Thanks guys, I think it will be important to share in this post some link to a page with information on how to use PWA in tests.

Cheers

 

Hi Miguel,

To use PWAs instead of OutSystems now to test your apps, you just need to have PWAs active in your environment. Doing that, the PWAs experience replace all the places we had linking to OutSystems Now experience.


Please check this link for more details

https://success.outsystems.com/Documentation/11/Delivering_Mobile_Apps/Early_Access_-_Distribute_as_a_progressive_web_app_(PWA)


Thanks

Hugo Gonçalves

Hugo Gonçalves wrote:

Miguel Verdasca wrote:

Thanks guys, I think it will be important to share in this post some link to a page with information on how to use PWA in tests.

Cheers

 

Hi Miguel,

To use PWAs instead of OutSystems now to test your apps, you just need to have PWAs active in your environment. Doing that, the PWAs experience replace all the places we had linking to OutSystems Now experience.


Please check this link for more details

https://success.outsystems.com/Documentation/11/Delivering_Mobile_Apps/Early_Access_-_Distribute_as_a_progressive_web_app_(PWA)


Thanks

Hugo Gonçalves

Hi Hugo,

Can one enable the PWA, while having self-signed certificate on the environment?

Regards,

Swatantra

 

Good that we have 2-3 months of overlap for people to transition from OS Now to PWAs. 

Good approach Hugo, it will be very useful! Thanks

Thanks Hugo for you clear explanation !

Regards

Hi Swatantra,

You'll need to run chrome with the following flag: --ignore-certificate-errors It will give a warning but it should work. 

If you don't use that flag, you won't be able to register the service worker, and, therefore, the app won't be recognized as a PWA.

Let me know if this answered your question.

Regards,

Ricardo Alves

PWA's do not support things like the barcode scanner, this is really bad. Outsytems now should only be deprecated when PWA functionality has had a chance to mature.

Joel Gold wrote:

PWA's do not support things like the barcode scanner, this is really bad. Outsytems now should only be deprecated when PWA functionality has had a chance to mature.

 Agree. 

 

I totally agree.  I would've just made a PWA if it weren't for needing to scan.  

Staff

Hi Joel, Abdul,


OS Now was always meant to be the way developers test native applications fast. Nowadays, the platform makes it even easier to develop custom native applications and test them fast.

Let me back-trace our steps from the early days of building mobile applications with OutSystems.

OS Now was the first solution we offered our developers and customers to build mobile applications. At the time, we even offered the native source code of OS Now so customers could brand the native experience and go to production with their our unique applications. 

Evolving the product, we made sure native applications could be generated easier, with less friction, and this meant a great deal of native customization was made available in low-code and generating the native application was made simple. We also introduced the ability to include different plugins other than the ones made available by the default OS Now. These two capabilities reduced the overall differentiation value of OS Now, as developers could now test their own specific customized native application, with only the native plugins they require. We still kept OS Now available so there would be a very quick way for developers to test the native applications that don't have specific needs for native plugins. Applications requiring access to specific native capabilities have always had the need to be generated - but again, this was made so simple.

With the introduction of PWAs, the testing of these types of applications became even easier than actually having a supporting native application for this purpose, and this rendered OS Now obsolete.


Kind Regards,

João Grazina


Grazina wrote:

Hi Joel, Abdul,


OS Now was always meant to be the way developers test native applications fast. Nowadays, the platform makes it even easier to develop custom native applications and test them fast.

Let me back-trace our steps from the early days of building mobile applications with OutSystems.

OS Now was the first solution we offered our developers and customers to build mobile applications. At the time, we even offered the native source code of OS Now so customers could brand the native experience and go to production with their our unique applications.

Evolving the product, we made sure native applications could be generated easier, with less friction, and this meant a great deal of native customization was made available in low-code and generating the native application was made simple. We also introduced the ability to include different plugins other than the ones made available by the default OS Now. These two capabilities reduced the overall differentiation value of OS Now, as developers could now test their own specific customized native application, with only the native plugins they require. We still kept OS Now available so there would be a very quick way for developers to test the native applications that don't have specific needs for native plugins. Applications requiring access to specific native capabilities have always had the need to be generated - but again, this was made so simple.

With the introduction of PWAs, the testing of these types of applications became even easier than actually having a supporting native application for this purpose, and this rendered OS Now obsolete.


Kind Regards,

João Grazina


 PWA  have very few  extensions, and most users will find that extensions they were used to in OSNow is not available for a PWA app, yet.  There is also the issue with PWAs in iOS that are brought back from the background freezing the screen elements, and there is no details for a simple true “fix” for that that I’ve seen on any of the forum questions on the topic, it’s basically creating dozens of handlers that create a undesirable user experience when the app is brought back from the background.


so with OSNow gone, developers of any apps that need extensions are left with little to work with, for the time being. Developing a native app seems like the only possible rout for apps that need a barcode scanner. That means many weeks and weeks just to get to “test” your app with even Google taking Up to 14 days to review an internal test track deployment.

I understand the hope for PWA, and I agree that if the features were in par it’s Preferred over maintaining OSNow, it’s just not there yet I guess  

 

Hello! I still use v10 so no PWAs.. we are planning migration to v11 in couple months but OutSystemsNow will end first.

I would like to know it will be removed from TestFlight and Stores early or end of November.


Hugo Gonçalves wrote:

Hello,


This month – July 2020 – we'll release Progressive Web Apps (PWAs) for everyone. In case you haven't heard about them yet, they're new mobile-optimized versions of web apps that you can install through your browser. They increase customer adoption and retention by engaging customers with frictionless experiences.


With PWAs, you'll also be able to test the look and feel of your native apps without having to generate a native build. With this new and improved testing capability enabled by PWAs, we will discontinue our existing OutSystems Now feature.


From Platform Server 11.9 onwards, the OutSystems Now experience will no longer be available in the development environment experience. OutSystems Now will still be available in Google Play and TestFlight until November 2020. After that date, we'll also remove it from Android and Apple stores.


OutSystems Now stopped being supported earlier this year, and we advise our customers to move to PWA mobile testing as soon as possible.


Thanks,

The OutSystems team

 

 Thanks for sharing this information. 

I would like to know it will be removed from TestFlight and Stores beginning or end of November.

Carolina Bessa wrote:

I would like to know it will be removed from TestFlight and Stores beginning or end of November.

 

Hi Carolina,

We still don't have a precise date when the OS Now will be removed from TestFlight and Google Play. When we know I will post here.

Thanks

Hi,

To help this transition we decided to give a little bit more time and keep the OutSystems Now on App Store until January 4th 2021. After that date, the OutSystems Now will no longer be available on Google Play and App Store.

Thanks,
Hugo Gonçalves


We have used OutsyemsNow in our regular web applications to enable barcode scanning. We do not want to write 2 applications. One for Web and  then another one for Mobile. Our web apps are mobile friendly enough except they they cannot access the phone hardware hence we used OutsystemsNow. 

Howe are you expecting us to proceed now that you remove OutsystemsNow.

Is the PWA feature available for regular web apps? We are on OS 11.

Thank you.

Hi Fabian,

Just to clarify, when you say regular web apps, you're talking about Traditional Web, right? If so, we're not planning on having PWA for Traditional Web Apps.

However, and on the bright side, web browsers can already leverage many of the mobile devices' capabilities. Web APIs already have access to camera, sensors, microphone, etc... You can look at a full list here.

This means that, programmatically, you can take advantage of many of these capabilities and use it in web applications. While we don't yet support an official web bar code scanning component, our Forge already offers some components, this QR Code Scanner, for instance, that you might explore. This might lead you in the right direction.

Let me know if this answered your question.

Regards,

Ricardo Alves

Hi Ricardo

Thank you for your reply. I will take a look at that QR code scanner and see if it works in our Traditional Web App. 

Fabian

Thanks for info

Champion

Thanks for sharing this information. It's really great.

Community GuidelinesBe kind and respectful, give credit to the original source of content, and search for duplicates before posting.