When creating the Open Transport API and its associated documentation, it would have been easy to fall into the the trap of just of just focusing on the technology tasks.
However, it was also a key consideration of the team to consider the User Experience of those systems that have adopted the Open Standard for transport and transit account interoperability.
We therefore followed (and will continue to follow) these principles wherever possible:
- Secure & trustworthy
This is customer data we are dealing with (albeit not PII : Personally Identifiable Information) so ensure that the solution can securely integrate and transfer the correct data – and make it clear to all that it is safe to use.
- Understandable & usable
Don’t create a solution that is too complex to initially set-up or maintain.
- Customer choice & control
The user should be fully in control of what accounts they integrate and know what data will be shared. They should also be allowed to break the integration whenever they want.
This integration is additional functionality that a user will see in their transport account, so try not to make it different from what they expect (e.g. avoid presenting jargon or technical stuff back to them).
Note: When using the term “User”, it is generally accepted that this refers to the end user of the solution (e.g. the customer using a browser). However, as this is a technical standard, we also wanted to ensure that we also made things as useful as possible for the technical user (e.g. the architect or developer) responsible for implementing the specification too.