Users need the ability to access the resources that are provided to them through a simple to use frontend but that presentation layer must be informed by some system in the context of the user performing an action. Different types of users have different types of resources provided to them and this information is provided by the backend to help the user leverage the APIs provided to them as quick as possible.
Assuming proper controls in the backend, how should we inform the frontend and thus the user? How can a user commit to actions on their APIs? Should we tie an API key to a user or instead have them register an application? How should we display this information to a user?
SheedGuy
commented
1 year ago
Users need the ability to access the resources that are provided to them through a simple to use frontend but that presentation layer must be informed by some system in the context of the user performing an action. Different types of users have different types of resources provided to them and this information is provided by the backend to help the user leverage the APIs provided to them as quick as possible.
Assuming proper controls in the backend, how should we inform the frontend and thus the user? How can a user commit to actions on their APIs? Should we tie an API key to a user or instead have them register an application? How should we display this information to a user?
Prior Art: