QAEM/DEV
Try EdgeOS Premium free for 7 days

Set up Launchify

Install Qaem Hub and the Launchify widget so your XENEON EDGE shows your apps as live tiles you can tap to launch or switch to.

By ·Updated

Launchify shows your apps as live tiles on the XENEON EDGE: tap one to launch it, tap again to bring its window forward. You'll install Qaem Hub, a free Windows app that runs Launchify's helper, import the widget in iCUE and pin your first app, with no account and nothing to configure.

Before you start

Install

Get Qaem Hub and the widget

  • Qaem Hub Setup.exe: the free app that runs Launchify's helper. Download it, or find it on the Downloads page.
  • launchify.icuewidget: the widget you import into iCUE, from the Elgato Marketplace. Launchify's product page links to it.

Install Qaem Hub and add Launchify Helper

Double-click Qaem Hub Setup.exe. It installs Qaem Hub for your Windows account, sets it to start with Windows and opens it. In Qaem Hub, open Add modules, select Launchify Helper and click Install selected. The module's details also have this setup as a step-by-step guide, Set up Launchify.

Import the widget in iCUE

  1. Open iCUE and select your XENEON EDGE from the device list.
  2. Go to the Widgets (dashboard) section for the screen.
  3. Choose Import widget and pick launchify.icuewidget.
  4. Drag Launchify onto a screen area and size it however you like.

Pin your first app

  1. Tap + in the header (or Add your first app).
  2. Choose where to look. Running now lists everything with a window right now, Installed lists your Start Menu and Desktop shortcuts, and Browse… opens a file picker for anything else.
  3. Tap an app to pin it. The row marks itself ✓ Added and the picker stays open, so keep going. To take one back off, tap the ✕ on its row twice.
  4. Tap ‹ when you're done. Your apps are waiting on the grid.
The Add an app picker with Discord and Steam marked Added, beside the Launchify grid of pinned apps
The picker stays open while you add apps.

Reading a tile

The dot and the line under each app's name tell you what the app is doing right now.

StateWhat you seeMeaning
ClosedDim iconNot running. A tap launches it.
RunningFilled dotA tap brings it forward.
MinimizedHollow dotA tap restores it.
In trayFaint hollow dot and In trayRunning with no window at all.
In frontAccent ringThe window you're in. By default, a tap minimizes it.
Close?Red tileWaiting for a second tap to confirm.
Launchify on a XENEON EDGE with tiles in front, running, minimized, in the tray and closed
Tiles in every state, with window counts, ×2 chips and monitor numbers.

Make it yours

Everything below is in the widget's gear, and in iCUE's own widget settings panel.

  • Assign every gesture. In Preferences → Touch, a tap gets three bindings (closed, running, in front), and double tap and long press get one each. Double tap is off by default, because binding it adds a short wait to every tap.
  • Arrange without the menu. Tap the pencil to put ‹ › ✕ on every app, so reordering and removing take one tap each.
  • Grid or list, any size. App size runs from 60% to 180%, and names and state lines can be turned off.
  • Colour the badges. The dot, the state line, the ×2 chip and the monitor number each have their own colour and their own switch.

Troubleshooting

The widget says "Waiting for Launchify Helper…"

Qaem Hub isn't running, or Launchify Helper isn't added or is switched off.

  • Tap Launch Launchify Helper on that screen. Qaem Hub opens, with Launchify Helper already picked in Add modules if it isn't added yet.
  • Or open Qaem Hub from the tray or the Start menu, and check that Launchify Helper is in Library and switched on.
  • The log file is still at %LOCALAPPDATA%\Launchify\helper.log.

Windows blocked the installer

Windows protected your PC appears for any installer that isn't code-signed, and Qaem Hub's isn't. Click More info → Run anyway. If your browser refused the download instead, choose Keep or Keep anyway in its downloads list.

An app shows as closed while it's clearly running

Launchify matches a pinned app to a running one by its exe path, falling back to the exe name.

  • Some launchers start a different copy of the exe than the shortcut points at (per-version folders, updaters). Re-pin the app from Running now while it's open, so you pin the exe that's actually in use.
  • Store apps that have never been started don't appear under Installed. Open the app once and pin it from Running now.

A window won't come to the front

Windows only lets the foreground app hand over focus. Launchify works around that, but two cases still win:

  • A full-screen exclusive game holds focus. Press Alt + Tab to leave the game first.
  • An app that's busy or not responding can't be brought forward until it answers. Use Force close in the app menu.

Moving an app to another monitor does nothing, or it snaps back

  • The app needs a window. A tray app has none to move.
  • Some apps manage their own placement and restore their saved position immediately. There's no way around that from outside the app.
  • Opens on waits about 12 seconds for the app's first window. An app that takes longer to draw one won't be placed.

An icon is missing or wrong

Icons are read from the exe and cached in %LOCALAPPDATA%\Launchify\icons. A few apps ship a stub exe with a generic icon. Delete that folder and the helper reads every icon again the next time the widget asks.

Uninstall

In Qaem Hub, open Launchify Helper's details and click Remove module, or uninstall Qaem Hub itself from its Settings. Neither brings back the old standalone helper. Remove the widget from iCUE separately.

Your pinned apps live in the widget's own storage, so removing the helper doesn't lose them.

Privacy

Launchify makes no network requests. Launchify Helper listens on 127.0.0.1:57131 for the widget on the same PC, and that's all its networking: no account, no telemetry, no cloud. Your pinned apps stay in the widget, and the icon cache and log stay in %LOCALAPPDATA%\Launchify.

Close app sends the same request as clicking an app's X, so an app with unsaved work still gets to ask you about it. Force close works like Task Manager's End task, which is why the widget asks twice first.