Phase 3 - Release Your App

Ensure your app meets Overwolf’s standards and is ready for launch. This phase will guide you through testing, submission, and managing your app’s release using the Developer Console.

Self test your app

Testing your app thoroughly before submission is key to creating a high-quality user experience. Make sure you test your app thoroughly in order avoid lengthy delays in the release of your app and to maintain a high quality user experience.

Submit your app

After you have sufficiently tested and debugged issues in your app. It's time to submit it.
Explore existing apps on the Overwolf Appstore to get design inspiration, and use this checklist to review your app before submitting.

Pre-submission Checklist

• Consistent Naming—ensure the Product Name (or Name) and Author parameters in the package.json in the app.asar are consistent across all versions.
• Digital Code Signatures—it is strongly recommended that you obtain a digital certificate so that Windows doesn’t alert you about the app installation. If you plan to host the app on the Overwolf app store the code signing is mandatory. For more information, see code signing.

• Custom Installer—choose the type of installer you want for your app. For more information, see Overwolf Electron Installer and complete the request form.
• CMP—review our CMP Documentation and confirm CMP integration into your app.
• Electron Game Event Provider—check the available games carefully on the Electron games support list and review the important notes provided by the Game events provider service.
• App Store Visibility—would your app be in the Overwolf Appstore (Web only)? If yes, fill in all the necessary assets and details in the Store Listing tab in the OW Console.
  note

  Electron apps are only available in the Web based app store and not in the Overwolf Native Client app store.

• Install the latest OW Electron Version—it is recommended ensuring the OW Electron Version is up to date. For more information on the latest OW-Electron version, see the Electron changelog.
• Subscriptions by Tebex—for Electron apps, only Tebex subscriptions are applicable. For more information, see Overwolf subscriptions by Tebex.
• Monetization—make sure you have designed your app to best utilize monetization strategies, even if at first you are not planning to monetize your app. For more information, see Monetization.
• Game compliance—make sure you have followed all of the game compliance guidelines. If you are making an app for a specific game, see the list of games with special compliance requirements. For more information, see Game compliance.
• User experience—take a fresh look at your app from the user’s perspective to ensure everything works intuitively.
• FTUE (First Time User Experience)—ensure your app introduces itself effectively to new users, highlighting key features.
• Advertising compliance—verify all ad placements follow Overwolf’s advertising policy and size requirements. For more information, see Advertising compliance.
• Hotkey Reminder—ensure a hotkey reminder is accessible in the settings or game window, allowing users to open/close the app easily.
• Resolution and compatibility—test your app across various screen resolutions and sizes, confirming that elements resize correctly and do not overlap.
• Second screen support—use a second screen to display your app while the game runs on the primary screen.

Submit Your App for Review

Submit your app to the DevRel QA team for review by uploading your latest build and filling out the necessary details in the Developer Console. The QA team will review your app and provide you with feedback and any additional requirements.

Use this submission form.

Typically the QA team will try to finish as quickly as possible, but be patient as they are quite thorough with their testing. The QA team will provide you with feedback as well as a review of the app itself.

QA Review Process

After submitting, your app will go through an initial QA cycle. Expect feedback on necessary adjustments, covering aspects like functionality, design, and compliance.

• Review Duration—the QA cycle includes initial testing, feedback, and retesting as needed to meet MVP standards.
• Review Checklist and Notes—the QA team will send you a checklist of identified issues to address in oder to complete the release process.

Developer's Console

After the initial submission passes the QA team, Overwolf will grant you access to the developer console.

The Overwolf Developer Console is your primary tool for managing app releases, tracking performance, and monitoring revenue. It provides a centralized interface to oversee all aspects of your app.

• Access and Permissions—after submission, you’ll gain access to the Developer Console. Manage permissions for team members to ensure each person has the appropriate access based on their role. For more information, see Access and Permissions.

• Release Management—Production and Testing Channels allow you yo upload builds to either for app release, or to the testing channel so that you can test your app in the real world.

• Console Tabs

  • Store Listing—customize your store page with descriptions and visual assets for users on the Overwolf App Store.
  • Game Stats—track analytics on game performance and user engagement.
  • Performance Stats—view metrics like DAU, installs, and retention rates (available post-launch).
  • Revenue Stats—monitor ad performance, including daily/monthly revenue, fill rates, and geographic breakdowns (available once ads are live).

For more information, see the [Developer's Console].