I see the TrustArc in use at quite a lot of sites - the fake delay, and the whole UX in general, is intensely irritating, and it just feels like the darkest of dark patterns. Really gives me a bad feeling about sites that use it.
Not just because of these dark patterns, but usability is messed up. The web should be redesigned to force standards compliant requiring websites to allow a “no script” support where you just go for information.
Cookies are not even remotely the largest problem on the fucked UX web we have today. It’s less about data delivery and ubiquity of the original WWW concept and more about “how do we force users to stay on our platform” or “how do we extract data on our users and sell it to the highest bidder.”
They also need to pass laws forcing companies who sign up users for services to have a graceful way to sign down and delete their account instead of these stupid cookie banners.
Unfortunately some cannot be helped as they just want to feel like they are helping/connecting with someone.
Sometimes, I swear the people I'd be helping knew they just didn't care, they were that desperate for human interaction.
It's a tale as old as time. I remember spending far too many hours as a kid convincing my grandmother not to send various people/fake businesses money (you owe the IRS! You power is going to be shut off!) and trying to curb her purchasing on QVC (I ended up later having a roommate who worked for them - the horror stories I could tell!).
So, increase the complexity. A certain number of savvy people will click off immediately, but they were likely too clever to bother with your game, so no love lost there. The ones who stick with it are your ideal targets. They'll wrestle through anything you throw at them to get what they want as long as you keep teasing that there's a light at the end of the tunnel.
However, you also can't make totally random, nonsensical design choices. They need to have a pattern that guides them in the darkness to the actions and outcomes you want most. It's your site after all, and no one can or will tell you how to run it as long as you show those retention and engagement numbers going up, so remember that.
Now that they're spinning in circles clicking on anything and everything trying to understand the labyrinth you've set out for them, you've got nothing to worry about. They've sunk their time and attention into solving this, and you're going to have them come back soon with a new strategy they're excited to try to beat the game. Once they feel like they've beaten you, you've won. They'll keep coming back just to prove to themselves that they've figured it out. They'll search on behalf of their friends and family, rising in their estimation.
Now they smirk and with just a hint of pride say whenever someone complains about how hard your site is to navigate, "Oh, it's not that hard. You've just got to know how it works."
> Subsets of IMDb data are available for access to customers for personal and non-commercial use. You can hold local copies of this data, and it is subject to our terms and conditions. Please refer to the Non-Commercial Licensing and copyright/license and verify compliance.
> The dataset files can be accessed and downloaded from https://datasets.imdbws.com/. The data is refreshed daily.
> Each dataset is contained in a gzipped, tab-separated-values (TSV) formatted file in the UTF-8 character set. The first line in each file contains headers that describe what is in each column. A ‘\N’ is used to denote that a particular field is missing or null for that title/name. The available datasets are as follows: [...]
I’d wager the license does not permit republishing the data on the web using better UX paradigms either—though I am too lazy to read through the fine print.
javascript:(function(){ window.location = window.location+'reviews?sort=userRating&dir=asc&ratingFilter=0' })()starbucks.co.uk works fine for me without trustarc, newrelic, googletagmanager or cloudflareinsights. No point executing all of that extra JS as its not for your benefit.
It does in the context of usability:
> What I remember learning was that any latency of more than 1/10th of a second (100ms) for the appearance of letters after typing them begins to negatively impact productivity (you instinctively slow down, less sure you have typed correctly, for example), but that below that level of latency productivity is essentially flat ...
> That's for visual feedback that a specific input has been received. Then there'd be a standard of responsiveness in a requested operation. If you click on a form button, getting visual feedback of that click (eg. the button displays a "depressed" look) within 100ms is still ideal, but after that you expect something else to happen. If nothing happens within a second or two, as others have said, you really wonder if it took the click or ignored it, thus the standard of displaying some sort of "working..." indicator when an operation might take more than a second before showing a clear effect (eg. waiting for a new window to pop up).
> but this delay is tens of seconds.
Oh, I wasn't aware of that - in that case it's ofcourse unjustified and definitely a "dark pattern".