UX debt is more user facing in nature than technical debt, but the vicious cycle that creates it is fundamentally the same:
- Product teams take design shortcuts, both intentionally (e.g. an inconsistent user flow that isn’t fixed to meet a product milestone) and unintentionally (e.g. an icon that unexpectedly confuses users)
- When left unaddressed, these shortcuts (“debt”) pile up and become increasingly difficult and impractical to fix (“pay down”)
- Eventually, UX debt begets more debt and the product degrades into an unfriendly, incoherent, and unusable user experience
I’ve decided to make an app with Ember.js. What sort of app you ask? The sort that will awesomely tell me what date to go on next week. Not the"How About We" interaction, but a personal app that will pick a random day next week, a date idea within a set distance of my location, and all of the accompanying information (like address/directions/links).
Perhaps an ability to download a calendar file, or perhaps a sync with Google calendar would be nice, but we’ll see about that one.
On to Ember tutorials.
That moment when you pick up your bag to realize you grabbed it upside down, and it was unzipped, and EVERYTHING JUST WENT EVERYWHERE.
I don’t mean to be so negative and point out the problems. I just want things to be easier and to work better.
I just care. A lot.