Crash & Burn: Revision history

Diff selection: Mark the radio buttons of the revisions to compare and hit enter or the button at the bottom.
Legend: (cur) = difference with latest revision, (prev) = difference with preceding revision, m = minor edit.

curprev 12:5712:57, 18 March 2026‎ Hmiguel talk contribs‎ 2,321 bytes +1‎ No edit summary
curprev 12:5712:57, 18 March 2026‎ Hmiguel talk contribs‎ 2,320 bytes +224‎ No edit summary
curprev 12:5012:50, 18 March 2026‎ Hmiguel talk contribs‎ 2,096 bytes +1‎ No edit summary
curprev 12:4812:48, 18 March 2026‎ Hmiguel talk contribs‎ 2,095 bytes −393‎ No edit summary

curprev 17:2517:25, 10 March 2026‎ Hmiguel talk contribs‎ 2,488 bytes 0‎ →‎Relation with other patterns
curprev 17:2417:24, 10 March 2026‎ Hmiguel talk contribs‎ 2,488 bytes +172‎ →‎Further reading
curprev 17:2217:22, 10 March 2026‎ Hmiguel talk contribs‎ 2,316 bytes −14‎ →‎Pattern Description

curprev 18:2318:23, 8 March 2026‎ Hmiguel talk contribs‎ 2,330 bytes +22‎ No edit summary
curprev 18:2118:21, 8 March 2026‎ Hmiguel talk contribs‎ 2,308 bytes +2,308‎ Created page with "=Summary= Intentional, simulated technical disruptions to deceive the user into believing a critical error has occurred. =Pattern Description= Crash & Burn introduces deliberate, fabricated system malfunctions to mislead the user into thinking the system has crashed. These cues mimic genuine technical failure and exploit user expectations of instability. The user may restart the system or the application, believing progress has been lost, only to later discover that the..."

Friction Design Archive

18 March 2026

10 March 2026

8 March 2026