> web API driven iOS and macOS applications) simply don't lead to these huge chains of functions I agree you don't see them collected together, as a rule, but

> web API driven iOS and macOS applications) simply don't lead to these huge chains of functions I agree you don't see them collected together, as a rule, but if you follow Results<> like this in those domains you see them being used multiple times on the backend before being yeilded to the frontend for further handling, resulting in chains that are just spread out a little bit more. Personally I've started exposing them through JSON at the API level to further extend the systems explicitness and idempotency.