Technology
The YOM technology framework represents a cutting-edge ecosystem designed to support the development, management, and delivery of highly interoperable browser-based UE5 experiences. Anchored in a decentralized architecture, this technology stack utilizes a blend of edge computing, peer-to-peer networking, Unreal Engine, AI, blockchain, web technologies, and pixel streaming.
These technological pillars enable YOM to offer dynamic platforms such as the Decentralized Cloud Gaming / Pixel Streaming Network (DePIN), the decentralized application (dApp), and the Software Development Kit (SDK). Together, these components create a robust environment for studios, artists, and developers to innovate and explore new realms within the Web3 space.
Technology Components
DePIN: DePIN is crucial for streaming high-quality digital content efficiently across the globe. Its sophisticated design minimizes latency and maximizes scalability, ensuring users anywhere can access content quickly and reliably.
dApp: The dApp is central to managing digital assets, configuring experiences, and engaging with the YOM community. Its wide range of functionalities includes asset management, user interaction tools, and community governance features, making it a comprehensive tool for ecosystem management.
SDK: The YOM SDK within Unreal Engine 5 offers a full suite of development tools that empower creators to build rich and interactive digital experiences. It encompasses everything from initial design to final deployment, providing a powerful resource for creators at every stage of development.
Key User Journeys
Creation: Developers create UE5 experiences using the SDK which can be easily deployed via app.yom.ooo to the DePIN and then streamed from any website or app.
Consumption: Players access and engage with these experiences via any platform. app or website through the DePIN, which needs to provide an instant, high-quality and seamless streaming service.
Participation: Community members use the YOM dApp to either engage in the community (e.g. voting, campaigns, social media) or to setup nodes that power the DePIN.
Non-Functional Qualities
To satisfy our user journeys, we defined the non-functional requirements, or the architectural qualities are defined as follows:
User Feedback: Measured through user feedback and technical performance assessments.
Authentication Speed: Speed and reliability of user access methods.
Latency: Regular testing to ensure latency remains below the 15 ms threshold.
Load: Capacity tests during peak traffic to ensure scalability under stress.
Security Audits: Frequency and outcomes of scheduled and random security audits.
Incident Reports: Tracking and resolution of security incidents.
Customization Utilization Rate: Frequency of use of customization features.
Developer Engagement: Active use and feedback on the modular tooling system.
Integration Points: Number of third-party integrations facilitated.
Cross-Platform Engagement Metrics: User interaction rates across different platforms.
Last updated