Why UX and FOSS clash and what we can do about it
summary
Argues that the real clash is an imagined user = programmer versus a non‑programmer user model, tracing it to Norman 1981 vs Unix rebuttals, and shows three collaboration modes: assimilation (“learn git”), company‑mediated processes, and a third way inspired by itch.io hobby games. Gives concrete practices: distribute as zip/executable, prefer SVN for binary assets, collect quick phone‑based feedback instead of formal tests, split work into assets/scripts/engine, and favor small‑team tooling that welcomes images and sketches rather than plain‑text‑only workflows.
AI-written summary · about
chapters (6)
- 0:00Introduction to UX and FOSS conflicts
- 1:26Historical roots of the clash
- 8:33Common collaboration models
- 12:22Hobbyist games as inspiration
- 18:20Summary and solutions
- 21:50Closing remarks and Q&A
related talks
28mWhy is UX so hard to contribute to FOSS
13mThe UX of UX - Behind the scenes of effectively designing in the open
57mI Am Your User, Why Do You Hate Me?
47mThe Hard Parts of Open Source
28mUX de guerrilla: manual de supervivencia para devs
49mCo-creating with UX and Software
51mHow UX Saved My DevOps
27mFrenemies in FOSS: How to deal with Charter Conflicts & competing efforts