When building Datelist, there is one thing I was sure of: to build great software, you need great UX. Software should be focused on bringing the most value possible to our users, with the less friction possible. And, when I talk about friction, there is one thing that always hurts: cookie consent banners.
I'll not try making a UX/UI lesson about them: first of all because I wouldn't be able to do so, but you don't need to be an expert to understand why they're bad.
Nobody reads them, it just interrupts the user flow
When building my app, I didn't want to find the best way to make it as hidden as possible or finding the best copy to force the users to accept something they wouldn't even read.
If you think more carefully about that, there is something deeply wrong with the way we force people to accept cookies on websites.
The solution was simple: Just get rid of cookies.
Despite anyone could find it, there is probably a mental shift to do when building apps these days. Third party cookies are not there for a long time anymore, so, when building an app, let's forget the classical "include those many scripts in your header" pattern, and let's build apps that don't use marketing cookies. That's not that hard, and it will save you problems later.
Bonus point: If you still need google analytics for your website, but don't want to use it for retargeting, you can keep doing it using the Cookieless Google Analytics Setup ;)