Controller Platform
Input across the hardware family.
Overview
What Controller Platform is
Research into input across the device family: how a controller is described to a developer as a profile, and how a session hands over between devices without changing input model mid-play.
System relationship
The stack every profile shares.
A device profile is a set of capabilities inside one platform (one library, one runtime, one Store, one account) rather than a separate product with its own ecosystem.
Shared software stack, 6 layers from top to bottom: 01 Games and applications, 02 Aevornix Store and library, 03 Aevornix account and identity, 04 Aevornix Runtime, 05 Operating and device services, 06 Home, handheld and cloud profiles.
Games and applicationsWhat a player actually runs, authored against a declared capability profile.Developer PreviewOpen
- Purpose
- What a player actually runs, authored against a declared capability profile.
- Development stage
- Developer Preview
- Related product
- Aevornix Engine
- Developer relevance
- This is your project. The profile you target is a build setting, not a separate port.
Aevornix Store and libraryDistribution, ownership and the library a player carries between devices.AvailableOpen
- Purpose
- Distribution, ownership and the library a player carries between devices.
- Development stage
- Available
- Related product
- Aevornix Store
- Developer relevance
- The distribution layer already runs in production, so it is the one part of this stack you can build against today.
Aevornix account and identityOne identity across the Store, the site, the tools and every device profile.AvailableOpen
- Purpose
- One identity across the Store, the site, the tools and every device profile.
- Development stage
- Available
- Related product
- Your account
- Developer relevance
- Entitlement and save ownership hang off this, so a player’s library is not per-device.
Aevornix RuntimePortable execution of compiled projects across supported targets.In DevelopmentOpen
- Purpose
- Portable execution of compiled projects across supported targets.
- Development stage
- In Development
- Related product
- Aevornix Runtime
- Developer relevance
- The compatibility contract. If your project runs on the runtime, moving between profiles is a capability question rather than a rewrite.
Operating and device servicesSystem services, permissions, storage, networking and application lifecycle.ResearchOpen
- Purpose
- System services, permissions, storage, networking and application lifecycle.
- Development stage
- Research
- Related product
- Aevornix OS
- Developer relevance
- Determines what a project may ask of a device, and how it starts, suspends and resumes.
Home, handheld and cloud profilesThe declared capability levels a build is certified against.Future PlatformOpen
- Purpose
- The declared capability levels a build is certified against.
- Development stage
- Future Platform
- Related product
- RVStack
- Developer relevance
- You target a profile, not a device. The profile is what the compatibility report is written against.
Research scope
- Input profiles declared per hardware profile
- Controller handover between devices
- Consistent input semantics across local and streamed play
Development
Where the work stands.
Objectives and dependencies. Dates appear only where a specific verifiable event backs them.
Research(1)
Input and controllers
Future PlatformResearch input profiles and controller handover across the hardware family.
- Depends on
- Hardware capability profiles
Related