If the devices are nearby, start locally
When devices are already nearby, a small task should not need an unnecessary round trip. We start with the local device, LANs and reachable private networks, and make the route and data destination understandable.
Local first does not mean every product is network-free. Sniptra focuses on local capture, SubnetDesk connects directly across reachable networks, and ArcRelay Suite explores collaboration between trusted devices. Each product must explain its own boundary.
Know the device before deciding what to share
You should be able to see who is connected, what is allowed and how to stop at any time. Pairing, fingerprint verification, permission scope and revocation are part of the product experience.
Being connected does not mean every action is authorized. Input, file and clipboard capabilities should express permission separately.
Do not make a product family feel like a bundle
Someone who needs screenshots should not have to install a full collaboration suite. Someone who needs private-network remote desktop should not have to operate a public rendezvous service.
Products can share foundations, but the task should decide whether they are used together. Sniptra is included in ArcRelay by default while keeping a path toward standalone use.
Be as clear about limits as capabilities
A launch candidate is not a released application. A platform roadmap is not complete support. Feature documentation distinguishes shipped capabilities, validation work and current limitations without promising unverified results.
When an operation fails, the product should explain what happened, whether a result was preserved and what the person can do next.
Finish one useful task before adding more features
Prove one reliable capture, transfer or connection before expanding. We care about task success, connection quality, inspectability and long-term maintenance, not just the number of features.
Browse feature documentation to see how these principles apply to each product.