"An interoperable communication library for the spatial internet."
⚡️ Current Supported Languages : C++, C#, WebAssembly
🖥️ Current Supported Platforms : Windows, Android, iOS and MacOS
Interoperability is the foundation of the spatial internet. We need experiences to work across multiple technologies in harmony, bridging applications and devices so that we can move beyond a series of disconnected islands.
The Connected Spaces Platform provides developers across a range of languages and platforms with a means to build interoperable, cross-reality, multi-user applications.
It comes in the form of an open-source client-side library, effectively encoding (in binary form) the standards by which applications can interoperably communicate with one another. Standards that we can all contribute to.
NPM packages are available for Web and Unity and can be found on npmjs.
-
Web: https://www.npmjs.com/package/connected-spaces-platform.web
-
Unity: https://www.npmjs.com/package/connected-spaces-platform.unity.core
- For detailed installation instructions head over here.
For C++ based applications, you can find headers and precompiled binaries for all platforms in Releases.
If you want to build CSP for your own use case follow the instructions below.
Build instructions for each supported language are below.
- Building for Web
- Building for C++
- Building for C#
- Building for Android
- Building for MacOS
- Building for IOS
If you choose to use the Connected Spaces Platform in conjunction with Magnopus Cloud Services, you'll need a Tenant ID.
Use this form to create a tenant in our staging environment.
If you are ready to use CSP in a live product, reach out to us to obtain a tenant in our production environment.
For more information about tenants and tenant IDs, visit our FAQ.
To help you get started using the Connected Spaces Platform, we have a set of examples for each supported language. We keep these examples up to date with each new major version of the library.
-
WebAssembly
-
C++
-
Unity C#
You can always find up-to-date documentation on the API here.
PRs are welcome! If have any ideas you would like to contribute please see our contribution page.