05-28-2020 13:25
05-28-2020 13:25
I am creating both a development and production version of my server-app (Python backend) that invokes the Web-API. Is it recommended to register two distinct apps (dev-app, prod-app) with FitBit, each getting its own unique OAuth2 Client ID? Or is there another common pattern or limitation I should take into account?
Thanks!.
Answered! Go to the Best Answer.
05-29-2020 14:39
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
05-29-2020 14:39
Hi @jniml55k,
Welcome to the forums!
I've seen many developers create multiple environments for their application; such as Test, QA, and Production environments. There aren't any restrictions on how many applications you can develop to meet your project needs, it really depends on you.
I find that this is effective in testing code changes on different environments other than your production environment, to ensure that you don't break your production environment when changes are applied.
I hope this helps. Let me know if you have any additional questions.
05-29-2020 14:39
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
05-29-2020 14:39
Hi @jniml55k,
Welcome to the forums!
I've seen many developers create multiple environments for their application; such as Test, QA, and Production environments. There aren't any restrictions on how many applications you can develop to meet your project needs, it really depends on you.
I find that this is effective in testing code changes on different environments other than your production environment, to ensure that you don't break your production environment when changes are applied.
I hope this helps. Let me know if you have any additional questions.