A Web Developer's Public Service Announcement on Autoplay
Description
A screenshot of a popular tweet from user Jake Williams (@MalwareJake), dated February 25, 2018. The tweet is a strongly worded rant directed at web developers. The full text reads: 'Dear web developers, The answer is zero. Zero. Get it through your thick skulls. Zero is the number of times anyone has EVER wanted something to autoplay on your site and start making noise. I'd honestly rather you mine crypto-currency in my browser than use my speakers. #kthxbye'. The tweet shows significant engagement with over 10,000 retweets and 41,000 likes. The humor comes from its aggressive, relatable frustration with a universally hated web feature: autoplaying audio. It humorously escalates the bad user experience by comparing it unfavorably to cryptojacking, a malicious activity. This resonates with senior developers who champion good UX and often have to argue against such features demanded by non-technical stakeholders
Comments
7Comment deleted
The fastest way to get a user to close a tab is with autoplay audio. It's like a speedrun competition for bounce rate
Ran an A/B test: Variant A autoplayed audio, Variant B quietly mined Monero; engagement stayed at 0%, but only one covered the Kubernetes bill - so congrats, “background-music.js” is now a design guideline
The irony of preferring silent CPU-melting cryptojacking over a 3-second marketing video perfectly captures the hierarchy of web annoyances - at least malware has the decency to suffer in silence while it steals your electricity
The fact that a security researcher would rather have their CPU cycles stolen for cryptocurrency mining than deal with autoplay audio perfectly captures the hierarchy of web annoyances: at least cryptojacking is silent. It's the ultimate indictment of autoplay - when malicious resource exploitation is preferable to your UX decisions, you've achieved a special kind of anti-pattern that belongs in a museum of terrible design choices, right next to `<blink>` tags and Flash intros
If your growth hack needs autoplay with sound, it’s not engagement - it’s an integration test for the mute button and Chrome’s MEI heuristic
Autoplay audio: the only web 'feature' where cryptojacking wins on UX grounds by respecting the principle of least astonishment
Autoplay audio: the only growth hack where Chrome’s default is no, Safari’s is lol-no, and user feedback is Cmd+W. If you must steal cycles, mint Monero in WASM - at least it’s quiet