Controller Guide
This chapter covers the types and use cases for MSST-Net client controllers.
What Is the Controller
The client controller is used to manage the MSST-Net client core.
Its main functions include:
- Configuring the client core
- Managing network connections
- Managing rooms
- Viewing device status
- Completing access authentication
The controller itself does not handle network connectivity.
Controller Types
MSST-Net currently provides the following controller implementations:
| Type | Platform | GUI | Remote Management |
|---|---|---|---|
| Tauri | Desktop | Yes | No |
| WebUI | Desktop / Server | Yes (browser) | Yes |
| Compose | Mobile | Yes | No |
Tauri Controller
The Tauri controller is for devices with a desktop environment.
Features:
- Local graphical interface
- Runs locally
- Full functionality
- Fast response
Supported platforms:
- Windows
- Linux
- macOS
Recommended for regular desktop users.
WebUI Controller
The WebUI controller is for headless devices or those requiring remote management.
Features:
- Browser-based access
- Supports remote management
- Flexible deployment
- No desktop environment required
Supported platforms:
- Servers
- Remote devices
- Headless devices
Recommended for server users.
Compose Controller
The Compose controller is for mobile devices.
Features:
- Native mobile interface
- Includes the client core
- No separate core installation needed
Supported platforms:
- Android
Recommended for mobile users.
How to Choose a Controller
Regular desktop users:
Use the Tauri controller.
Server users:
Use the WebUI controller.
Mobile users:
Use the Compose controller.
Notes
Configuration data is generally compatible across different controllers, but specific behavior may vary by platform.
Choose the controller that best fits your device type.
Next Steps
After choosing your controller:
- Install the client
- Complete access authentication
See: