anchorWhat Is Webex App Hub

The Webex App Hub is an ecosystem of third-party and Cisco-built integrations, bots, service apps, and embedded apps. These apps are purpose-built and allow Webex users to bring their external workflows into Webex to expand their current productivity. By publishing your app on the App Hub, your product or service is introduced to thousands of daily users looking to discover new tools that will amplify their workflow.

Follow the submission steps outlined in this article as a guide on how to get your app published on the App Hub. If you prefer to keep your app private, that's not an issue! Even if you create an app and choose not to submit it, users in your Webex Org can still add your app without it being publicly available.

Still in? Great!

anchorReview Process

To be published on the App Hub, all submissions will go through a thorough review process. In the first phase of the review process, the team will review all required public facing marketing materials. In the second phase, we will conduct functionality and usability testing. Throughout this process, the team will communicate and work directly with you to meet all requirements via email. Once you submit, a ticket is opened with the review team, and they will respond with the next steps.

Here is a list of some general things that we will be looking for:

• NO grammatical errors, foul language, or obscene images
• All stated features are fully operational (Production Ready, No Demo/Test Integrations)
• No third-party advertisements or references/mentions to Webex competitors
• NO "Cisco", "Spark", "Webex", "Teams", or other Cisco trademarks in the app title or logo without express permission from Cisco
• Use of minimal scopes necessary for your submission to operate
• Bots Only (Must responds to commands like: "hi," "help," or "hello" when someone messages it for the first time)

Once all requirements have been met, your app will be published to the Webex App Hub.

anchorHow To Submit

Once you are ready to submit, you can click the button labeled “Submit to Webex App Hub” on the application’s registration form.

When you submit, you will receive an automated email stating that your submission has been received. During the review process, the App Hub team will validate all the below outlined items. If any changes need to be made, you will receive an email from the App Hub team with the requested proposed changes. The review process is transparent, and depending on how quickly the proposed changes are addressed. The review process can move very quickly. Once all form fields are reviewed and are deemed satisfactory. The technical review of the submission will begin.

The technical review stage is where the App Hub team test your submission using demo Webex accounts. Depending on the type of submission, and the provided testing instructions. Testing will vary, as some submission types have multiple contexts in which they can operate. We do test your submission on all applicable major OS and Device platforms to include, Apple (iPad, MacOS, iPhone), Microsoft Windows (Desktop), Android OS (Tablet, Phone). We will test all stated functionality thoroughly, along with evaluating the overall user experience. All proposed required changes will be communicated within the subsequent email thread that was sent as confirmation your submission was received.

anchorSubmission Guidelines

Please carefully review the following sections below, as these are the required fields that you will need to fill out within the submission portal.

The Submission Name

The name of your submission should not begin with the words "Cisco" or "Webex". They can be appended at the end of your app name. Example: "My App for Webex".

Logo

Your logo cannot contain any Webex or Cisco branding in it.

Description

The description should incorporate at a minimum all of the following:

1. A short sentence describing what your organization does. For example, “My Org specializes in productivity and collaboration services that helps the world be more effective.”
2. A short sentence describing what your app does. For example, “My App is a Webex integration that enables sales teams to sell more in Webex Meetings.”
3. A list of benefits that your app brings to the Webex ecosystem.
4. A sentence that starts with “To use My App, …” followed by a set of prerequisites a Webex user will need to get started with using your app. Do users need to have an account with your organization? Do users need to have a paid or free Webex Account?
5. If the app is not entirely a free service, we always ask that you add an additional sentence that includes where to find more information on pricing. If you do not want to share this information publicly, then you can say something like “Please contact our sales team at example.com for questions on pricing.” If the app is a free service, then say that explicitly here.

The Integration Scopes

When selecting scopes for your submission, you should select the minimum necessary scopes for your app to function. This is to ensure that a user is not being asked to authorize more access than is necessary which can raise a security concern.

The Summary

The summary is the set of text that will appear below the app name on the App Hub. This needs to be a unique string of text, and it cannot be the same as the first line of your app description. The summary should also not be derived from any other text areas within the submission form.

Categories

You can choose up to three categories that describe your submission. Users will filter through apps on the App Hub by selecting these categories.

Landing Page

The landing page is a publicly accessible page that serves as a informational page on "how to get started" with your app. This page cannot require any authentication to access it. The landing page also must be hosted on your organization's web domain, and be a page solely dedicated to showcasing/sharing information about your app.

Also be sure to adhere to the Cisco Webex Branding Guidelines when designing your landing page. If Webex or Cisco logos are used, they must be the most up-to-date versions. Additionally, when spelling Webex, make sure the "e" in ex is not capitalized.

Contact

This contact name and email should be for an actual person who will be responsible for responding to the Webex App Hub Review team when changes to the submission need to be made. Please ensure that the contact entered has access to the Webex account that is associated with your app that was created in the Webex Developer Portal. We often see a generic email address, such as support@example.com or engineering@example.com. Such generic emails will not be accepted.

anchorMultiple Submission Guidelines

The following section covers guidelines for submitting multiple app submissions.

Bots

• Developers can submit multiple bots, granted they are distinct and can be easily differentiated from other bots already submitted by the same company. Points of differentiation should encompass, but are not limited to, the bot's description, logo, and use case.

• Bots that require an integration to function, can either have their integration submission listed or the bot submission listed on App Hub, but not both. As general guidance, if you have an integration already listed on App Hub. You should update the current integration listing with the bot's email address instead of making a bot submission.

Integrations (Meetings, Messaging, Contact Center, Calling, Service App)

• Developers can submit multiple integrations, granted they are distinct and can be easily differentiated from other integrations already submitted by the same company. Points of differentiation should encompass, but are not limited to, the integration's description, logo, and use case. Additionally, for multiple integrations from the same company, evidence of each integration being sold under its own separate SKU is required.

Embedded Apps (In-Meeting, In-Space, Sidebar)

• Developers can submit multiple Embedded Apps, granted they are distinct and can be easily differentiated from other embedded apps submitted by the same company. Points of differentiation should encompass, but are not limited to, the Embedded App's description, logo, and use case. Additionally, for multiple Embedded Apps from the same company, evidence of each Embedded App being sold under its own separate SKU is required.

• Embedded Apps featuring multiple App Contexts (Sidebar, In-Space, In-Meeting) will be considered a single listing on App Hub. And will not be allowed to be submitted as separate listings.

anchorNeed Some Help? We Got You Covered

We are excited to provide you with support for your App Hub submission. If you need help, the Webex Developer Support Team is standing by and happy to point you in the right direction. You can also start or join a conversation on Webex for Developers Community Forum.

anchorApp Hub Resources

My AppsCreate a New AppExplore App Hub