Every feature carries a maintenance bill that comes due long after the launch post. The useful discipline is deciding, up front, who is going to pay it.
This piece walks through how we think about it at Paycux, what we have changed our minds about, and where the sharp edges are.
Why session revocation matters
That brings us to why session revocation matters. Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Ship the smallest version that is honest about its limits. A feature that does one thing completely beats one that does five things with an asterisk on each.
Getting started with the Sessions API
Getting started with the Sessions API is where this gets concrete. Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
- Choose defaults as carefully as features
- Settle the name before you ship the thing
- Ship the smallest honest version
- Say plainly what the feature does not do
Prerequisites
Prerequisites deserves its own treatment. Ship the smallest version that is honest about its limits. A feature that does one thing completely beats one that does five things with an asterisk on each.
Naming is design work. If the team argues about what to call something, the disagreement is usually about what it is, and shipping before that is settled means shipping the confusion to customers.
List a user’s active sessions
List a user’s active sessions deserves its own treatment. Naming is design work. If the team argues about what to call something, the disagreement is usually about what it is, and shipping before that is settled means shipping the confusion to customers.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Ship the smallest version that is honest about its limits.
Revoke a session by ID
That brings us to revoke a session by id. Ship the smallest version that is honest about its limits. A feature that does one thing completely beats one that does five things with an asterisk on each.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Building “Sign out everywhere”
Building “Sign out everywhere” deserves its own treatment. Ship the smallest version that is honest about its limits. A feature that does one thing completely beats one that does five things with an asterisk on each.
Naming is design work. If the team argues about what to call something, the disagreement is usually about what it is, and shipping before that is settled means shipping the confusion to customers.
Best practices & implementation tips
Consider best practices & implementation tips. Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Where this leaves us
If there is one thing worth taking away, it is that the expensive decisions are the ones made implicitly. Making them on purpose costs an afternoon.
If you are working through the same problem and want to compare notes, the docs cover the mechanics and the console shows the behaviour on your own data.
Everything here, already built
Sign-in, enterprise SSO, directory provisioning, roles and an audit trail behind one API. Start with the quickstart and have a working sign-in this afternoon.