You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we deploy a feature that relies on a Prismic release, we need to be able to QA that feature with the Prismic preview on mobile devices, including Android and Apple tablets and/or mobile phones. This is because more than 80% of our customers buy online using a mobile device. The engineering team therefore uses a mobile-first development approach.
Using the devTool device simulator is not enough to seriously QA a feature as it doesn't always accurately mock the behaviour of mobile devices.
It would be really useful (in fact, essential) to be able to load a Prismic preview on all mobile devices as this would improve our confidence when deploying a new feature to our website and the speed of our delivery.
The text was updated successfully, but these errors were encountered:
Could you share more information about your test setup on mobile devices? Especially which browsers you're using? Is it only IOS, or also Android, etc.
The toolbar is supposed to work seamlessly on Chrome across various devices. Unfortunately, previews cannot work on Safari because of its cookie policy.
When we deploy a feature that relies on a Prismic release, we need to be able to QA that feature with the Prismic preview on mobile devices, including Android and Apple tablets and/or mobile phones. This is because more than 80% of our customers buy online using a mobile device. The engineering team therefore uses a mobile-first development approach.
Using the devTool device simulator is not enough to seriously QA a feature as it doesn't always accurately mock the behaviour of mobile devices.
It would be really useful (in fact, essential) to be able to load a Prismic preview on all mobile devices as this would improve our confidence when deploying a new feature to our website and the speed of our delivery.
The text was updated successfully, but these errors were encountered: