[cco]

We recently released isagent.dev [1] exactly for this reason!

Internally at Stytch three sets of folks had been working on similar paths here, e.g. device auth for agents, serving a different documentation experience to agents vs human developers etc and we realized it all comes down to a brand new class of users on your properties: agents.

IsAgent was born because we wanted a quick and easy way to identify whether a user agent on your website was an agent (user permissioned agent, not a "bot" or crawler) or a human, and then give you a super clean <IsAgent /> and <IsHuman /> component to use.

Super early days on it, happy to hear others are thinking about the same problem/opportunity.

[1] GitHub here: http://github.com/stytchauth/is-agent

[gavmor]

I feel OP is addressing the complementary, opposite use case in which behavior is to be unified across user agents.

[cco]

> Mostly I’ve just been stressing to my team that we need to consider these interfaces for our application as equal surfaces for how our application will be used. As we build features, we need to make conscious decisions about whether and how those features are accessible and legible in all three of those interfaces.

I read this to mean that they're thinking about all three experiences (interfaces) on equal footing, not as a unified one experience for all three user agents.