Closed RhodesPeter closed 7 years ago
Update:
@MHemsley, we have been collecting opinions regarding PWAs and the performance of our app.
Our concern is that Apple OS doesn't properly support PWAs (they don't allow service workers). Our PO is mainly using iPads which means that by creating a PWA it would be optimised for devices that our PO doesn't use.
We have just tested our app (the prototype) on a new iPad and the janky animations are a big issue. On our phones (android), safari (on laptop) and chrome the animations flow smoothly with no jank. We think that the jank may be specific to iPad, in which case we may be able to fix the problem without the need to create a PWA.
Update:
The suggestion to create a PWA was based on the janky animations that the PO was experiencing on her iPad. We have tested this on an ipad (and iPad simulator on xCode) and have managed to reproduced the jank.
We looked at our code on Chrome DevTools and can see that the way we have created the animations is putting a big strain on the CPU. I have added an image below. This strain on chrome (on our Macs) is not a problem but obviously is a problem on iPad. I suggest that we create an animation using GSAP (which is much more efficient) for the first sprint and we can test this with Jasmin. If this is the root of our problem then we can let the PWA dream go for now.
I am closing this issue as we have decided against creating a PWA.
At user testing on the 28/03/17 we linked the CAHMS iPad up to the Wifi rather than an internal sim card and the issues with slowness between pages were no longer present.
Set up PWA in project. This should be done before additional pages are created.
Related to issue #57