Safari technology preview vs safari2/19/2023 ![]() Well, three versions later and those bugs have not been fixed. ![]() For the time-being I chose to use them separately in regular Safari, on the assumption that these egregious issues would be quickly fixed in the next STP version. Starting with around STP 124 I started experiencing consistent crashes on some websites, making them completely unusable in STP. It’s also highly problematic when new versions are flat-out broken. This is bafflingly hostile behaviour for what is supposed to be a beta version of the browser that users voluntarily, out of charity, help Apple debug. Product feature, safari, safari technology preview 64 update*, web push notifications.Apple try to make it impossible to revert to a prior version of Safari Technology Preview (STP) – and they also try to force updates to the latest version immediately, without user consent. If you want to get started with Aimtell, go ahead and sign up for our 14-day free trial. What are your thoughts on this possible change? Is this something you’d like to see on other browsers as well? Let us know by sending us a message! Implementing the user gesture rule should not result in a loss of new subscribers, and may in fact help you in the long run. As marketers, your ultimate goal should always be to provide your users with the best possible user experience. That’s all we have to report on for now! Should this update come to Safari, you shouldn’t be concerned. It isn’t a sure thing that this update will come to Safari, but it is good to keep it in mind should the feature go live in the near future. ![]() This browser allows developers and users to test out new features that may be released to Safari. The upside to this is that you are showing it to the maximum amount of people, but the risk of course is that your users will deny your request because they haven’t yet learned of the value of your push notifications.Īs a quick note- remember that this update is currently being tested with Safari Technology Preview. If you have the default settings in place, your prompt will display to everyone immediately when they land at your website, and therefore the Safari update would impact your subscribers. In that case, this update likely wouldn’t impact you at all. For example, you might already have a prompt condition that has your opt-in prompt display once a user has scrolled down 20% of a page, or once they have been at your site for 30 seconds. In fact, it may help improve opt-in rates! Alternatively, you might not even notice a difference if you are already employing some of our custom opt-in prompt features.Īs an Aimtell user, you have a lot of control over your opt-in prompts, including how they look if you choose a custom prompt type, and when they display by using our prompt management controls. Impact on Opt-In Ratesĭoes this update mean you will see a sharp decline in opt-ins? We don’t think so. We’ve discussed this idea in the past as well and how it may result in poor UX. Why the change? In an effort to further improve user experience, this update would ensure that opt-in requests aren’t displayed immediately when a user lands at a website. While not a huge change, it is certainly worth mentioning. ![]() This update would require a user gesture to take place (such as a mouse click) before the request to send push notifications would be displayed. By choosing to opt-in, the user grants you permission to send them web push notifications. As you already know, before you can send anyone a web push notification, they first have to opt-in. With that in mind, we wanted to let you all know of a possible change coming to Safari.Ī new feature was released as part of Safari Technology Preview 64 that will impact your permission requests. Do some of your users use Safari as their web browser? More than likely at least some of them do, as it’s one of the more popular browsers out there today. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |