Over the last few months, all developers saw a new interface when they logged in to their developer accounts. This new developer portal is the home base for managing your use of the new Twitter API, with continual improvements and new features to help you build. We’re planning to create new ways to manage access for multiple development environments, to help you rethink how you manage a team of collaborators, track and understand your API usage, move up and down between access levels, and find resources to help you be successful. If you have other ideas you’d like to see, let us know and share your feedback!
We’ve also introduced "Projects" within the developer portal as a way to organize your work and manage your access to the Twitter API for each use case you’re building with it. We’re starting with just one Project per developer account for the first Early Access release, so you can begin using Basic access to the new Twitter API.
With the recent release of the Academic Research product track, eligible researchers can now add a Project in the Academic Research product track. They may also create or maintain another Project in the Standard product track for a distinct, and separate use case.
As we roll out further access levels and product tracks, you’ll be able to create multiple Projects for different use cases. We plan to support separate production, staging and development Apps within a Project as distinct environments to help you better manage your integration, and make it easier for a team to manage a Project and its Apps. For now, you can still use your existing, standalone Apps and create new ones if you need to; eventually, all API access will be through Projects.