Skip to content

Hardware setup

Prepare a computer, a phone with the matching App installed, and MemoMind glasses that support plugin execution.

Preparation checklist#

Item to prepareHow to check
ComputerChoose desktop Studio for your OS: Windows 10/11 x64 uses an EXE and requires Edge WebView2 Runtime; macOS uses a Universal DMG supporting Intel/Apple silicon; Linux x64 requires an actual released executable.
PhoneInstall the MemoMind App that matches this toolkit, sign in with the developer account that owns the application, and locate Settings → Memo Lab → Developer Workspace. The current QR scanner supports Android/iOS. Confirm scanner availability before using other platforms.
GlassesCharge the glasses, unfold the temples, put them on and keep them powered on. Enable phone Bluetooth, connect through MemoMind App and confirm that the App reports connected. Pairing in system Bluetooth alone is insufficient; the firmware must also support the current SDK ABI.
LANConnect the computer and phone to the same router or mutually reachable networks. The computer may use Ethernet while the phone uses Wi-Fi. Guest Wi-Fi, AP isolation, VPNs and firewalls can block access. LAN connectivity provides a download path, not application access permissions.
Release packageAfter cloning with Git or extracting the complete archive, you should have GlassSDK/, PhoneSDK/ and Studio/. On Windows, look in Studio/windows/; on macOS, look in Studio/macos/. Keep the toolkit after installing the Mac app and import it into Studio.

Record your environment for troubleshooting#

  • Record the SDK release, Studio file version, phone OS and App versions, and glasses model and firmware version.
  • If Developer Workspace is missing from the App, obtain the matching test App and firmware from your toolkit provider. Do not follow old documentation to look for a Debug entry that has moved.
  • For the first run, use the supplied matching SDK, Studio, App and firmware. Before upgrading any component, record the old versions, then recheck connectivity, installation and core features.

Before developing hardware features#

Once the devices are ready, look up the public APIs for your intended feature. Canvas size, display controls, raw IMU, audio and device information each have specific entry points. The presence of hardware does not by itself mean a plugin can access it.

Reference files in the toolkit#

  • Studio/README.md
  • GlassSDK/docs/INSTALLATION.md