As part of our ongoing improvements to our paywall, we’ve successfully released v.3, the third version of our paywall. One of the missions of the core development team here at InPlayer is to remove barriers to migration and integration with the InPlayer paywall. We aim to delight our customers with the paywall’s flexibility, stability, and ease-of-use.
V.3, the new version of our paywall has brought a couple of new functionalities, better called “benefits”, enabling agility and rapidity to address any technical needs our merchants would have to support their businesses.
Our objective with the InPlayer Paywall is to provide customers the best user experience with the latest fixes and improvements without any disruption. Merchants will also have the power to push out changes quickly and easily across apps or connected devices – empowering them to always provide a consistent experience.
As more of our merchants have the need for enriched video offerings, with end-users at the forefront, our white-label revenue generating paywall for full scale audiences – across web, connected devices and OTT platforms – will provide detailed insights and predictions on subscribers’ engagement, present a solid starting point for discovering the potential strengths and weaknesses of your video business.
Believing third time is always lucky, turns out to be true for our newest version of the paywall app. We’ve imagined a more optimized version of the app that loads faster with much better performances and a re-written UI. Alongside paywall v.3, we also released a new version of our JS SDK library, allowing us to develop changes and additions much faster in the future.
Specifically, we have done the following:
As mentioned above, the v.3 version represents a fully re-written application, using the typescript programming language. In the future, when a merchant has a specific feature requirement, this optimization will allow faster optimization of both the app functions as well as the code structure, ensuring app expansion with new functionalities which ensure the highest conversion rates for our clients.
In addition to the rewrite of the paywall application, we also updated the code for our JS SDK tool which we also use for the development of the paywall app. This adds to the speed of the development cycle, allowing us to develop and debug with much more clarity and speed.
If you are a merchant utilizing our JS SDK to create custom end-user flows, this new version includes some new methods that simplify that process and makes for an easy use of the JS SDK library.
From a visual standpoint, we have optimized and enriched the design without introducing breaking changes and keeping the same end-user flow that is simple, intuitive and easy-to-use. The other aspect of the design improvement is in the code of the design itself. Here, we worked on a mechanism to ensure only the needed design code to display a specific screen is loaded, thus providing a sleek and optimized user- experience.
Last but not least, the new v.3 version includes some optimization of the application code as well, addressing some of the difficulties merchants have had with instantiating the app on their website. We have created some additional methods to the paywall app that can be used to better manage the app on your websites and avoid having issues.
We hope you’re as excited about these paywall benefits as we are. See the Paywall in action and for more information:
As part of our ongoing improvements to our paywall, we’ve successfully released v.3, the third version of our paywall. One of the missions of the core development team here at InPlayer is to remove barriers to migration and integration with the InPlayer paywall. We aim to delight our customers with the paywall’s flexibility, stability, and ease-of-use.
V.3, the new version of our paywall has brought a couple of new functionalities, better called “benefits”, enabling agility and rapidity to address any technical needs our merchants would have to support their businesses.
Our objective with the InPlayer Paywall is to provide customers the best user experience with the latest fixes and improvements without any disruption. Merchants will also have the power to push out changes quickly and easily across apps or connected devices – empowering them to always provide a consistent experience.
As more of our merchants have the need for enriched video offerings, with end-users at the forefront, our white-label revenue generating paywall for full scale audiences – across web, connected devices and OTT platforms – will provide detailed insights and predictions on subscribers’ engagement, present a solid starting point for discovering the potential strengths and weaknesses of your video business.
Believing third time is always lucky, turns out to be true for our newest version of the paywall app. We’ve imagined a more optimized version of the app that loads faster with much better performances and a re-written UI. Alongside paywall v.3, we also released a new version of our JS SDK library, allowing us to develop changes and additions much faster in the future.
Specifically, we have done the following:
As mentioned above, the v.3 version represents a fully re-written application, using the typescript programming language. In the future, when a merchant has a specific feature requirement, this optimization will allow faster optimization of both the app functions as well as the code structure, ensuring app expansion with new functionalities which ensure the highest conversion rates for our clients.
In addition to the rewrite of the paywall application, we also updated the code for our JS SDK tool which we also use for the development of the paywall app. This adds to the speed of the development cycle, allowing us to develop and debug with much more clarity and speed.
If you are a merchant utilizing our JS SDK to create custom end-user flows, this new version includes some new methods that simplify that process and makes for an easy use of the JS SDK library.
From a visual standpoint, we have optimized and enriched the design without introducing breaking changes and keeping the same end-user flow that is simple, intuitive and easy-to-use. The other aspect of the design improvement is in the code of the design itself. Here, we worked on a mechanism to ensure only the needed design code to display a specific screen is loaded, thus providing a sleek and optimized user- experience.
Last but not least, the new v.3 version includes some optimization of the application code as well, addressing some of the difficulties merchants have had with instantiating the app on their website. We have created some additional methods to the paywall app that can be used to better manage the app on your websites and avoid having issues.
We hope you’re as excited about these paywall benefits as we are. See the Paywall in action and for more information:
Start maximizing the value of your content with InPlayer’s new Landing Page Builder We’ve been building beautiful landing pages for your online events for some time now, but finally you…
Do you want to run reports effectively? Are you wasting too much time on report creation? At InPlayer we care a lot about our customers needs. We have listened closely…
While a substantial volume of content today on the Internet is free, premium and quality content costs more to create and requires different types of content protection models to monetize…
