[btbuildem]

I keep revisiting this approach over and over again - I don't know, maybe I never learn. I'm not interested in analytics dashboards, my context is more around stringing together prototype/poc services into workflow pipelines. The idea usually is along the lines of "have an orchestrator service that knows what the user is trying to do, and serves a sequence of specific, embedded micro-UIs backed by services that implement each step of the overall process". I can't seem to shake this "do one thing and do it well" unix motto, and keep wanting to bring it over to UX design.

[sollewitt]

I worked on a project exploring this idea and an issue is that while each step in a user journey (get restaurants near me, show me menus, make an order, show me on a map) could invoke a distinct service, provided by different providers that just do that thing well, they all want ownership of the experience and the precious user data and prefer to consume input and render output rather provide output data for others to use - there’s no stdout to pipe. The upshot is apps do everything, which is the opposite of the Unix philosophy.