Versions Compared

Version Old Version 46 New Version 47
Changes made by

Nathan Wailes

Nathan Wailes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 2017.11.01 - Twitter - patio11 - Tweetstorm on US/Japan IRL/Web UX
    • Japan IRL UX (good):
      • What:
        • if you found literally any gov't in America as efficient as Ogaki City Hall, surprising.
        • I was done in 25 minutes. 3 minutes with greeter, 10 minutes with forms, 3 minutes with each of 4 adjacent bureaucrats who passed me along.
        • "Mr. McKenzie congrats on joining national health insurance, here's your card. This is your first time on it, right? Want explanation?"
    • Japan web UX (bad):
      • What: 
        • Think of every annoyance you've ever found in any shipping application. Forms which clear all inputs on an error. Ridiculous timeouts.
        • Office hours. Unclear instructions. Telling the user to do things a computer would do better, like formatting input to match a regexp.
        • Non-sensical browser restrictions, invariably to an old version of IE. Proprietary authentication schemes. No design, functional or visual.
        • Take all of the problems you've seen in the set of all American web applications. Take the union of them. Cross-apply to all Japanese apps.
      • Why:
        • Deeply entrenched reasons. Most apps are built by systems integrators. Huge skills gap in dev population. Devaluation of devs generally.
        • Large (shrinking) install base of legacy phones w/ unique UX requirements and lowest-common-denominator apps by purchasing decree.
        • Decisionmakers for purchase/implementation are often not merely not technical but Deeply Not Technical; not routine computer/etc users.
  • Building a Princess-Saving App
    • Rec'd by Patrick Collison here

Courses / Tutorials

...