Build & Deploy
Build your Unity project into an APK and deploy it to Board hardware.
Building your project
Build an APK
- Open File > Build Settings (Unity 6+: File > Build Profiles)
- Ensure your scenes are added to the build list
- Click Build and choose a location for your APK
Tip: For development builds, enable Development Build in Build Settings to access debugging features including the debug overlay.
Player settings to verify
- Architecture: ARM64 (
arm64-v8a). Board rejects APKs built for other architectures. - Minimum API Level: API Level 33.
- Scripting backend: IL2CPP.
- Package Name (Player Settings > Other Settings): this is the package you’ll pass to
board-connect launch <package>.
Install and Launch
The Board exposes Board Connect, its built-in HTTP API, so there’s no USB cable involved. The Board shows its address under Settings > System.
Legacy:
bdb(USB serial) is still available if you need it. See thebdbreference. Board Connect is the documented path.
From a browser (human)
- Open the Board Connect web UI in your browser, using the address shown under Settings > System on the Board.
- Drag your
.apkonto the page to install it. - Launch the game from the Library or Settings > Sideloaded Apps.
With an agent (board-connect)
The board-connect CLI is the agent-facing Board Connect client — no ADB, no scripts. Install it from dev.board.fun/connect/install. You only pass the Board’s address to pair; that saves it as the default, so every later command resolves the target on its own:
board-connect pair <host>— run once; the user taps Approve on the device.board-connect install path/to/your-game.apk --launch— install the built APK and bring it to the foreground.board-connect launch com.yourcompany.yourgame— launch it by package name.board-connect logs com.yourcompany.yourgame— tail the app’s logs (add--followto stream live).board-connect screenshot --out shot.png— capture the screen.
The <package> is your Unity Package Name (Player Settings > Other Settings). See the full Board Connect reference for pairing, status, and app management.
Viewing Logs
Stream the app’s logs over Board Connect: from a browser, the Board Connect web UI shows logs for an installed app; with an agent, use board-connect logs com.yourcompany.yourgame --follow while the app runs.
Troubleshooting
Board not detected
| Symptom | Fix |
|---|---|
| The web UI or agent can’t reach the Board | Confirm you’re using the Board’s current address from Settings > System and that your machine is on the same network (Board Connect listens on port 8843 over the LAN). |
| Pairing fails or is rejected | Re-run board-connect pair <host> (pass --force to mint a fresh token) and have the user tap Approve on the device. The Board’s address is shown under Settings > System. |
Installation fails
| Symptom | Fix |
|---|---|
| The Board rejects the APK | Ensure the APK was built for ARM64 (arm64-v8a) — Board rejects APKs built for other architectures. |
| Build or install errors on API level | Confirm Minimum API Level 33 in Unity Player Settings. |
| Not enough room on the device | Verify sufficient storage on Board (board-connect status shows device readiness). |
App crashes on launch
- Stream logs to see the crash:
board-connect logs com.yourcompany.yourgame --follow - Rebuild with Development Build enabled for more detailed errors
- Check that all required settings are configured (see Setup Reference)
Next Steps
- Sample Scene - Explore SDK features
- Simulator - Test without hardware
- Touch Input - Handle Piece and finger input