Hi Guys,I am wondering if anyone knows something about this behavior with PWAs.We use a Zebra scanning device with Android (I guess Jelly Bean) for some of our Apps. The first problem was, that Chrome is not available on Zebra and Chromium afak has no PWA option. So I installed Edge as Browser on the scanner and was able to save the PWA.What happens was, that the adjustments of the app where totally gone and it was not usable as PWA.This is the view in the Edge PWA.
After this fail I downloaded Firefox and the result was totally fine.
I am wondering if this is a known MS Edge misbehavior because than it definitely needs to take into considerations when distributing the App.Does anyone have any experience with Edge and PWAs yet?
Best regs!
Tobias
Hi,
I have never used Edge on mobile devices before but to check your issue I used one of my existing PWA to add on my device using edge browser. It working perfactly fine.
But I want to mention here is that my PWA is build with pure OutSystemsUI theme, there is no extra styling. May there there is some customer styling because of which it is happening. If that is not the case then it can be edge issue on specific device type.
Hi Tobias,
PWAs on Microsoft Edge (Chromium) are very much supported. Microsoft has documented below pre-requisites for PWA support on her documentation:
To run as a PWA, your server-hosted web app should include following minimum requirements.
localhost
To be a great PWA, your app must also meet the following requirements.
It looks the issue is with the design layout which is not quite matching per MS requirement.
Regards,
Swatantra
Hi Guys,
thanks for your replies! I tested some other PWAs on the Zebra device and all of them shown the same behaviour with Edge.
I would assume that it has something to do with the "old" android version. I currently have no other Android device to test. But I will organize one with a newer version and test again.
As all our Apps are B2E I will advise the user not to use edge to load the PWAs.
Best regards!
Old android could be the reason. By the way did you check if the requirements for PWAs on edge as mentioned above in the table complies in the app.