From VR to Seven Screens: Solving Input, Progression, and Social Presence

In "From VR to Flat Screens: Bridging the Input and Immersion Gap," Dany Lepage takes us through the architectural journey of adapting a successful VR title for seven non-VR platforms.

3 min readInfoQ
From VR to Seven Screens: Solving Input, Progression, and Social Presence

Porting a VR title to seven flat-screen platforms is not a story about rendering pipelines or input remapping. It is a story about how a team confronted the unglamorous, deeply human work of preserving a product's essence when the hardware that defined it disappears. Dany Lepage's candid breakdown of that journey is the most useful kind of technical talk: it refuses to hide behind architecture diagrams and instead forces us to ask what we are actually building for.

The core insight here is that cross-progression and input diversity are not engineering chores. They are product decisions. When your game was designed for hand-tracked presence in a 3D space, moving to a phone screen or a controller means rethinking what the player is doing moment to moment, not just which button maps to which action. Lepage's team had to solve for the fact that a player on Steam might have a keyboard, a player on iOS has a touchscreen, and a player on PlayStation has a controller, all while sharing the same progression state. That is not a technical problem with a technical solution. It is a design problem that demands you decide what stays constant across those experiences. If the input changes, the feel changes, and if the feel changes, the game changes.

But the more uncomfortable lesson is the one Lepage frames as the "product fit" gap. Translating social presence to 2D screens is not about adding a chat window or emotes. It is about accepting that the emotional register of sitting next to someone in a virtual room does not survive contact with a flat rectangle. The team had to ask what made the original experience valuable to players and then decide how much of that value could be rebuilt in a medium that strips away spatial cues and physical proximity. That is a humbling exercise, and Lepage's willingness to share the friction, the false starts, and the compromises is rare. Most postmortems polish the rough edges; this one seems to leave them visible.

What does this mean for you? If you are building cross-platform experiences, stop treating platform support as a checklist. The hard work is not maintaining release velocity across seven stores. It is maintaining a coherent vision of what the player is doing and why it matters, regardless of the screen in front of them. Lepage's team did not solve the problem by making the game identical everywhere. They solved it by deciding what could bend without breaking the experience. That is the takeaway worth carrying forward: the goal is not parity. The goal is a version of the experience that earns its place on each platform, with all the trade-offs that implies.

From InfoQ

Dany Lepage discusses the architectural journey of porting a hit VR title to seven non-VR platforms. He explains how his team solved the challenges of cross-progression, diverse input paradigms, and maintaining release velocity across Steam, iOS, and PlayStation. Beyond the tech, he shares candid lessons on the "product fit" gap when translating immersive social presence to 2D screens.

Read the original at InfoQ