Let’s dive right in. Complianz 7 is a rework of a considerable chunk of our entire codebase, creating a React back-end and optimized handling on the front end.
There are three main reasons we reworked our codebase, and will give you a glimpse into Complianz’s future:
WordPress and Gutenberg
Gutenberg is a React framework that offers site editing for WordPress. Gutenberg has been developing for a while and should add React to the WordPress back-end. To integrate seamlessly when the time has come, Complianz is built in React to eventually integrate and feel like a native WordPress app.
Headless and Cloudless in the Future
Finishing the rework allows us to look at upcoming technical challenges for native solutions.
Headless and/or Static solutions are increasingly popular due to performance and security. Complianz has yet to offer an out-of-the-box solution, as it requires building towards a more client-side approach. Like many cloud solutions, a client-side approach is also a disadvantage when dealing with compliance. Integrating with plugins, themes, and WordPress, which are written in server-side code, is hard to control directly in a browser.
Solution: Complianz ‘On-Premise’
It will become increasingly difficult for website owners to comply with privacy guidelines in the coming years.
Services like Google and Facebook are proposing less transparent, server-side solutions that will shift them more towards GDPR or equivalent than ePrivacy. This will make way for misunderstood compliance and technical implementations for website owners.
Cookieless doesn’t mean privacy-friendly by default, and server-side handling has a severe downside of transparency and control by the end-user and offers technical challenges for the website owner.
In a spectrum of services, with different approaches, guidelines, privacy laws, and additional frameworks like the TCF, an increase in ‘solving’ privacy for monetization leads to confusion for end-users.
Complianz is doubling down on the easiest solution to comply.