CraftController

PRODUCT RESEARCH / 21 NOVEMBER 2026

Layouts are one part.
The receiver matters.

CraftController will use the existing Windows DSU Manager receiver. We are not building another desktop connector.

This review compares published product documentation, not measured performance or hands-on results. The current Android revision is untested at the user's request.

What other tools offer

DSU Controller

Its guide documents a browser-based drag/drop layout editor, QR layout transfer, several layouts, motion configuration and Windows DSU Manager pairing.

Useful lesson: make templates and transfer simple. Layout QR transfer and PC pairing are different operations.

Original guide

DroidJoy

A Windows receiver provides XInput emulation. Template customization, two sticks, sensors, Wi-Fi/Bluetooth and multiple clients are documented.

Useful lesson: simplify setup around a clear receiver and configurable starter layouts.

Official product page

Monect PC Remote

Its store listing advertises custom layouts, sensors, a Layout Store, mouse/keyboard, remote screen access and other PC tools.

Useful lesson: reusable layouts help, but CraftController should keep its controller workflow focused rather than copy the whole remote-desktop suite.

Developer's listing

Steam Input and AntiMicroX add useful lessons about readable action labels, mapping sets and profiles. They are different products: the cited Steam touch menus use a trackpad, while AntiMicroX maps an existing gamepad to desktop actions. Neither is evidence of an interchangeable phone-to-DSU Manager implementation.

What we are doing now

Implemented in source

  • CraftController name, retaining the existing Android package ID.
  • Windows PC setup screen for the receiver you already use.
  • Phone endpoint display, refresh, explicit copy/share and honest subscription status.
  • Original layout editor, four presets, colors, dead zone and button haptics retained.

Integration gate still open

The original guide pairs with a QR code generated by DSU Manager. The public guide does not define the control handshake.

We need the installed Manager version and its pairing protocol before implementing that step. Copying a phone address is not a replacement. No “Connected” screen or hardware compatibility claim is fabricated.

Customization roadmap

  1. Establish and implement the actual Manager pairing contract first.
  2. Add named game profiles with duplicate, rename and delete.
  3. Add undo/redo, optional snapping and an accessible hidden-control list.
  4. Add validated, versioned offline profile import/export.
  5. Keep action labels separate from real output bindings; then consider remapping, physical-controller input and receiver-validated motion.

Version 0.4 adds QR scanning and reviewed PC endpoint storage; it does not complete pairing. Profiles, macros, motion, rumble and physical-controller forwarding remain unimplemented. Their place on a roadmap is not a support claim.

Thanks and independence

Thank you to breeze2 for DSU Controller and DSU Manager, and to the cemuhook-protocol authors for documenting DSU. CraftController is independently implemented and is not an endorsed release of those applications.

The full document includes the comparison matrix, primary-source links, evidence limitations, pairing blockers and implementation priorities.