Overwolf

Overwolf

  • Getting Started
  • Docs
  • API
  • Events Status
  • Blog
  • Q&A
  • Support

›Best Practices

Best Practices

  • Overview
  • App specific experience
  • First time user experience
  • App launch performance
  • Marketing Communications
  • User journey and error handling
  • Per-game settings
  • Hotkey best practices
  • Second monitor usage
  • Data persistence
  • Reduce OPK size
  • Use Tab as an app Hotkey
  • Type definition file
  • Download Link with referral ID
  • Video capture best practices
  • Enable Developer Tools

Using Windows API

  • Using Overwolf windows
  • Windows Communication
  • Windows Types
  • Resolution Size and Position
  • General Tips

Using Plugins

  • Plugins overview
  • Plug-in Implementation
  • Write your own plugin
  • Sample plugin
  • Simple I/O plugin
  • TeamSpeak plugin
  • Downloader plugin
  • Process Manager plugin

Using Events

  • JavaScript events overview
  • Using game events in your app
  • Game events Simulator
  • Verifying event status

Developers Console

  • Submit a new version
  • Submit for review
  • Update store listing
  • Manage your subscriptions
  • Users and permissions
  • Crash reports
  • Rating and reviews

Integrations

  • Integrating app analytics
  • Login with Twitch
  • Login with Overwolf
  • Event SDK for Game Devs
  • Twitch Extensions

Request a Service

  • Marketing asset requirements
  • Looking for Group
  • Promoting your app

Community Help

  • Join the Community
  • Webinars
  • Developers Content
  • Code snippets

Legal

  • Legal overview
  • App terms
  • Developers terms
Edit

User journey and error handling

User Journey Basics

  1. The journey you build for users should make them understand your app's value as well as how to actually get it.
  2. Each step and possible action in your app needs to be communicated clearly to your users.
  3. Software issues are inevitable, and error messages are super important to help users address the issue or, at least, avoid confusion.

Desktop journey

The desktop window is a great place to provide information and lead the user onwards - since most apps and features are meant for in-game usage, users launching the desktop app are more attentive and patient. In this window you can explain your app's basics, clearly state what it does and where (for example, 'go in-game to launch this app').

The desktop window can be home to plenty more. Sharing news, asking for feedback, showcasing a cool video and more - it's all possible in your desktop hub.

CS:GO Stats CS:GO Stats Lolwiz Lolwiz PUBG Tracker PUBG Tracker

Loading screens

Good loading screens for your app assist in monetization and provide a great opportunity to communicate with the user in a non-interruptive way. You should include a short reasoning for the loading screen itself (for example, 'fetching player information'), but can also include visuals, materials or texts.

Streamaware Streamaware DotaPlus DotaPlus

App data is ready

When your app is ready to work as intended, let the user know and explain how they should use it initially. It’s super important to make sure that users understand the basics and are able to use your app as intended with hotkeys and/or mouse clicks.

Koreanbuilds Koreanbuilds DotaPlus DotaPlus

Error handling

Having a downtime? Server being upgraded? Something else is wrong? Your users have to know. A simple and accurate error message announcing the state of the app can go a long way and save you time, energy and bad reviews. We recommend figuring out the most common issues and implementing error messages whenever possible.

Examples of error messages:

  • “Due to a recent game patch, Overwolf app API has stopped working - we'll fix it shortly!”
  • “[app name] is not able to show stats because the chosen game mode is not supported.”
  • “We’re experiencing issues and this app is currently unavailable.”
  • “Some stats may be unavailable. Check <appname's> Facebook and Twitter for updates”
Herowatch Herowatch Herowatch Herowatch Lolwiz Lolwiz
Last updated on 2019-8-27 by Shoomanjin
← Marketing CommunicationsPer-game settings →
  • User Journey Basics
    • Desktop journey
    • Loading screens
    • App data is ready
    • Error handling
  • Legal
  • Terms overview
  • Developer's terms
  • App terms
  • Overwolf terms
  • Overwolf Privacy policy
  • Support
  • Questions and Answers
  • Discord
  • Slack
  • Facebook
  • Twitter
  • Documentation
  • Changelog
  • API
  • App Creation Process
  • Best Practices
  • Game Events status
  • Information
  • Careers
  • Fund
  • Developers Blog
  • Overwolf Appstore
  • Advertise on Overwolf