Forum Topic - FRCAPI What should I use for a production app?: (5 Items)
   
FRCAPI What should I use for a production app?  
Where should I get credentials for use in a published app for interacting with the FIRST API? Should I use  my personal 
credentials (I'm assuming not) or some custom generates credentials
Re: FRCAPI What should I use for a production app?  
Hello,
We don't support distribution of apps that interact directly with the API, unless each user has their own key. For 
example, if you want to publish an app to the store, you can either A) cache the data on your server, so that users are 
interacting wiht your server or B) prompt the user to enter their credentials in the app, and then use those credentials
 for each request.
Thank you.
Re: FRCAPI What should I use for a production app?  
I see. Would you prefer for me to actually cache requests and periodically update them or would just forwarding all API 
requests to the FIRST API after appending my credentials be okay? I'm assuming that would become more of a problem once 
a large mass of users starts using the app, and this system is probably not meant to handle that much traffic.
Re: FRCAPI What should I use for a production app?  
So the main reason we do this is that if we have to disable a token (or if one gets disabled because of traffic) we 
don't want to cause a lot of users to go down. So, if you just append your token, it will cause all the users to stop 
working. Caching the data and having users re-fresh off of it would ensure you can control how often the requests happen
, since only one source is making requests.
Re: FRCAPI What should I use for a production app?  
Makes sense. I might just have the app access a pre existing api cache online and if someone wants to actually contact 
FIRST's api they'll have to use the token. Thanks for the quick responses!