In the current flow to create an application you have to navigate in "Audience > Org/Group > Applications > Create Application. But that isn't intuitive and it messes up the UX.
Usually, when a new API is created, an application is required to promote it on the staging environment. The user clicks on the "Applications" button, and there isn't the option of "Create Application" there, just the list of Applications.
I think the "Create Application" option should be included there and the Org/Group option should be displayed as an option in the form.

3 places where new application functionality makes sense:

• audience > account > applications (done): account is fixed, user needs to select an app plan (select with search) available for applications on the current account.
• audience > applications: user needs to specify account (select with search) & app plan (select with search) to which an application for the selected account could subscribe to.
• [API name] > applications: service is fixed, user needs to specify account (select with search) & app plan (select with search) for the current service.

The idea is to use specific pages for each of those forms, but the same form partial with different items pre-selected depending on the context (i.e. only apps for account A when in audience > accounts > account > apps) and different collections available (i.e.only app plans for service A when in service A).

(Another option would be to always re-direct user to one page for app creation but to me this is sub-optimal as the user would loose context and we need to redirect based on values sent)

Dev Notes

This comes from https://github.com/3scale/porta/pull/47#issuecomment-424670452