![]() ![]() ![]() Searching for ways to streamline the process, I noticed that often the solution description diagrams were the most informative element of the document - and the part requiring the most review time and effort.įor each new solution document, I had to spend time reverse engineering how a particular author chose to visually represent authorization servers, access tokens vs ID tokens, APIs or web applications, and so on. Reviewing solution proposals was eating more and more time! That's an excellent problem to have, but a problem nonetheless. With the company's explosive growth, the number of engagements taking advantage of our extensibility points to implement advanced solutions kept multiplying at an amazing rate. ultimately, it's the magic sauce behind the feeling of effortless success that is typical of a well-crafted tool.Īfter joining Auth0 last year, one of my first responsibilities was to review a large number of solution proposals. Far from being just a frivolous desire to make everything beautiful, thoughtful design is what makes everything easier to understand and use: it eliminates unnecessary distractions, emphasizes what's salient, nudges without forcing. One of the things I enjoy most about working at Auth0 is the pivotal role design plays in nearly everything we do. Tweet This A Visual Language for Identity
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |