Web push notifications as a communication channel is meant to work on HTTPS websites only. HTTP websites availed web push notifications by creating sub-domains on HTTPS, making it a two-step subscription process. In the first step, websites can set up the context with an interactive message on a custom dialog box while the actual subscription prompt appears in the second step.
Flow HTTPS vs HTTP on Chrome Mobile
Two-step subscription process is a better approach as the website visitor can be made aware of the kind of updates the user will receive through web push notifications. Having said that, it often results in lesser subscriptions as a majority of the website visitors drop off at the first step itself. Around a year back, we came up with 1-click subscription process for HTTP websites providing a near-native subscription experience to the website visitors. Our customers operating on HTTP websites, who tried a 1-click subscription process on their domain, experienced a sudden jump in the number of subscriptions - and they simply loved it!
1-Click Subscription Flow on HTTP
1-Click subscription process involves invoking the subscription prompt of an HTTPS domain onto an HTTP page using an iFrame. But with the release of Chrome 62, the 1-Click subscription process won’t be supported on HTTP websites anymore. This may lead to a drop in your daily subscription rate.
The motivation behind the change:
- Aligning notification permissions with push notifications - Notification permission and push notifications should work in tandem. You can't have a different set of guidelines / rules for HTTP and HTTPS websites.
- Removing confusion for users about the domain they’re subscribing to.
- Increasing reliability for native subscriptions.
Following the objectives mentioned above, the usage of notification permission from iFrames was deprecated in Chrome 59.
Impact of the change:
Notification permission from insecure origins and within iFrames won’t be supported anymore. Thus, 1-Click subscription process on HTTP websites will be stopped.
|Main-frame||Insecured Context||Not Supported|
|iFrame||Secured Context||Not Supported|
|iFrame||Insecured Context||Not Supported|
This change is supposed to go-live around 17th Oct with the release of Chrome 62 as per the Chrome release plan.
What’s our take on this?
We, at iZooto, believe it was an open bug used as a feature, which had a limited lifetime. Contextual subscriptions make more sense in the longer run. As the adoption of push notifications is increasing with domains, and users are more aware of the fact that push notifications can be spammy at times, they’re more conscious about the domain they are subscribing to. Do read our blog post on how to set up optimal subscription process on your domain.
Please note that this change will only affect websites running on HTTP. Write to us at firstname.lastname@example.org if you need any help in setting up a new subscription process for your domain.