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.
Prerequisites
Prerequisites 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.
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.
Step 0: Test with Paycux default credentials (optional)
Step 0: Test with Paycux default credentials (optional) is where this gets concrete. 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.
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.
- 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
Step 1: Get the Redirect URI and Outbound Email Domains from Paycux
Step 1: Get the Redirect URI and Outbound Email Domains from Paycux 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.
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.
Step 2: Retrieve your Apple Team ID
Step 2: Retrieve your Apple Team ID 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.
Naming is design work.
Step 3: Register an App ID
Consider step 3: register an app 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.
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.
Step 4: Register a Service ID
Consider step 4: register a service id. 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.
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.
Step 5: Register a private key
That brings us to step 5: register a private key. 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.
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.