10yr ago today I tweeted <suggestion to @Amazon: You know I have a #kindle, have "send sample to kindle" and "buy on kindle now" right under the "buy it now" button>. Sometime since then, they took my advice! ;)
If it doesn't start with an API, one will never be implemented without a full rewrite.
If an API is added later, it will never be complete or correct.
If you define an API and then implement the UI/UX so that it works some other way than calling the API, then neither the UI/UX or the API will be correct or secure.
If a feature can't be defined as a set of API calls, it's not defined enough to implement well.
In honor of the morrow: https://historynewsnetwork.org/article/1493
@email@example.com @firstname.lastname@example.org @email@example.com @firstname.lastname@example.org @email@example.com @firstname.lastname@example.org I'm old enough to remember when Concur was a refreshing change from whatever godawful Oracle thing we used before that.
@email@example.com @firstname.lastname@example.org We should name this the Concur effect.
1) decision makers are not direct users
2) features are overwhelming and disjointed
3) user experience gets worse over time
Dear @matrix : I want to like you, I really do, but your onboarding process needs help. I literally have 35 years of experience figuring out how to set up weird network services, and I still can't get Matrix or Riot to work.
Genie: You have ONE WISH.
Me: Alright, I have one, but it's very detailed.
Genie: As long as it is only one wish, you're allowed to spend as much time as you want detailing it.
Me: Alright, here we go. *Grabs notebook and takes a deep breath* The key words MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL are to be interpreted as described in [RFC2119].
Genie: Wait, is that...?
Me: *Flips notebook* Chapter 1. Preamble.