Focusing on SaaS rather than B2C. A clear advantage of getting users build their own UI is that processes emerge as a consequence. Specific roles within a team

Focusing on SaaS rather than B2C. A clear advantage of getting users build their own UI is that processes emerge as a consequence. Specific roles within a team don’t use every feature in an UI, and often compose a series of actions in a workflow. Letting them build the UI to aggregate and automate leads to being able to extract business knowledge in the UI as well as the reasoning the user has with AI about what to build. Put that in a SaaS for an office and the outcome is the true representation of work being done in that office, plus clear signals about edge cases (aka “the user is not using his custom built flow, why?) In a sense, related to https://danieldelaney.net/normal/ https://danieldelaney.net/normal/ Stability etc can be handled post-hoc: once a customized ui proves some benefits (via user adoption, or whatever you think efficiently measures productivity gains), it can be formalized by a human coder, who gets the full picture and has all the domain knowledge baked in, as long as you don’t capture UIs only but also the reasoning that built it. Back to article: smart to think this in terms of browser, since that crosses the boundary between SaaS