Why is it required to wait for approval before starting development?

[dialogflow_util]

While other communication platforms (like Alexa, Facebook, etc) essentially have two stages to application development: development & production, why does Twitter seem to have a single stage, where I need to have fully-formed information about my application, come apply, wait 2-3 weeks (per other threads), and then develop + deploy the app? Sorry, just another person griping about being in the “Waiting” queue for access to the sandbox level of premium webhooks.

[happycamper]

As beta applications come in, we are doing our best to quickly process those that have a well-defined use case and explain how they plan to use the APIs. Those that don’t match those criteria often require email correspondence, to understand what it is you are actually trying to do with the API, which takes us time.

Please confirm your email on the account you used to apply and respond quickly to our review team if there are followup questions about your application. Or you can share your app ID here for us to check on.

[dialogflow_util]

Thanks @happycamper - I got approved the other day and was able to conform our integration to the new API, which was great! I was just worried seeing people complain about waiting for weeks.

In terms of process, it also seemed like a bit of a challenge for us that we’ll need to make an application on behalf of each of our corporate clients and wait on approval before we can do our integration work (rather than integrate + then approve), but that’s not the end of the world, especially if approval is pretty quick.