Where the Install Button Used to Be

7:00 PM on a certain evening. A middle schooler wolfs down dinner like a school meal and enters their room. A link pops up in a group chat. Upon clicking it, a 2010s masterpiece awakens right in a browser tab—no loading bars, no installation prompts, and no device spec warnings. The character is already moving before the opening music even starts.

Another instance of the same game is open in the adjacent tab. The map is identical, but the protagonist has been swapped for a cat created by a friend, and the enemies throw math problems. The friend who made it didn't write a single line of code. They simply spent an hour last evening writing out their desired rules in sentences. Change it to a cat. Have the enemies throw multiplication tables when they attack. Make the boss room door open when they're all solved.

The two jump between each other's versions with voice chat turned on. One laughs, while the other tweaks the rules on the spot. The revised version becomes a new link and drops into the group chat again. Before 9:00 PM, six variations of the same game pile up in the room.

At the same time, the dashboard of the studio that created the original work logs the number of derivatives that branched off from their game over the past day. Someone looks at the list in anger, while someone else schedules a meeting to discuss incorporating the most played variation into the main game. Whether or not revenue is attached to this will be determined by the contract in place at that time.

This has not happened yet. It is also difficult to definitively say it will be several years down the line. The events cited in the memo occurred not in the distant future, but over the past few weeks, and prerequisites like browser support rates are already met. All that remains is who will sort out the tools and rights first.

A Memo is Made Public

Microsoft has set up a separate laboratory in its gaming division. This came to light on October 14 when an internal memo sent by Xbox leader Asha Sharma was published in its entirety. The name is Xbox Labs, and the URL is labs.xbox.com. It is a small organization grouping game makers, engineers, and scientists, headed by Scott.

The memo primarily addressed what has been happening outside rather than the company's own roadmap. In recent weeks, games have been rapidly decompiled and rebuilt, starting to run on hardware never originally intended. Windows PC builds are translated for Apple Silicon and executed within browsers via WebAssembly and WebGPU. Sharma included a figure noting that global browser support for WebGPU is approaching 90%. She added that the more surprising part lies elsewhere: the world's biggest games are being remixed into the source codes of other games.

Three Shaken Assumptions

Sharma stated that these experiments are shaking the premises the industry has long held onto: the assumption that software and hardware are tied together, the assumption that there is a line between those who make and those who play, and the assumption that the way people discover and experience games is fixed.

The wording of the memo was not defensive. It noted that making games easier to access, breathing life back into old games, and turning more players into creators and co-creators are undeniably positive outcomes. It added that this remains true even if it clashes with existing business models.

Why Games are Next

As a rationale for establishing Labs, Sharma brought up AI agents. The reason coding became the first major task for agents is clear: it can be written, executed, and tested. The memo argues that games share this exact nature. Scale was also factored in. People spend 72 billion hours a year on Xbox games, roughly five times the estimated time spent writing code globally. Labs stated it would build in public and measure success by whether more people play and create.

How Creators Read It: If the Term 'Build Target' Disappears

Currently, the thickest block on a small team's schedule is porting. Releasing on PC, getting console certification, and recoding for mobile takes months. In the direction pointed out by the memo, that block becomes thinner. Pass the build spat out by the engine through WebAssembly once, and the browser immediately becomes the platform.

The difference is stark when imagining an investment meeting. Now, you turn your laptop around to play a video, and the other party watches with crossed arms. In this altered world, you send a link. The other party plays it themselves for thirty seconds on their phone and looks up. If it's not fun, it ends right there; if it is, the next question follows on the spot. The demo transitions from documents to experiences.

Conversely, some blocks become heavier. Saying it runs anywhere goes hand in hand with saying it can be ripped apart anywhere. The practice of hiding and protecting code loses power, leaving the logic on the server, continuously updated content, and the community as the remaining lines of defense. When a solo-developed game splinters into ten branches in a single day, whether to view it as infringement or distribution becomes a matter the creator must determine in advance.

How Publishers Read It: Selling Discovery, Not Distribution

As installation and store reviews thin out, one lever held by publishers shrinks. This means the value of the ability to put games on a platform itself drops. What, then, is left? The judgment to pick this particular one out of thousands, the power to gather people in the first week, and labor-intensive tasks like localization and operation.

Contract clauses are also likely to change. The stipulation of platform-specific exclusivity loses meaning in the face of builds that run anywhere. Instead, lines like these will increase: Remixes are permitted only for non-commercial purposes. If a derivative exceeds 100,000 monthly plays, revenue is shared with the original creator. Variations using original characters must be registered on an approved list. Currently, no one has a standard, and Labs has not presented one either.

How the Industry Reads It: Who Draws the Line in the Gray Area First

The most cautious sentence in the memo is the section on IP. There is a reason they specifically added that they would remain responsible stewards. Ripping apart a game and putting it inside another game is not cleanly sorted out by current law. The speed at which agents can accomplish this overnight is now layered on top of the path fan porting and emulation have walked for decades.

We can also picture a conference room scene that will take place someday. On one side, data showing that a million derivatives actually boosted the original's sales is presented, while on the other side sits a letter of protest from a studio whose universe was morphed into a mockery. The platform holder's decision to establish a public laboratory to look into this process reads as a declaration that they intend to draw the line internally before it is drawn from the outside.

Engine companies face the same questions. Sharma's explanation that models write scenes well thanks to text-based scene formats equates to saying that engines with open formats will have an advantage in the agent era. Keeping them closed is safe but excludes them from training data, while leaving them open spreads them quickly but sacrifices control.

How Users Read It: The Sense of Ownership Wavering

The first palpable change is simple. Clicking a link sent by a friend just starts a game. There is no download size and no checking of device specs. The scene of a game—once playable only on a dead retro console in a drawer—awakening in the browser of an old laptop is part of this same current. This is what the memo meant by breathing new life into old games.

In return, a familiar sensation is shaken: ownership. Logging in one day, you might be greeted by a sentence like this: This title's service has ended and it can no longer be played. Back when files were on our devices, we could at least take out a dusty disc to look at. If it becomes a session that is merely loaded, even that possibility vanishes. The memo did not address this point.

And Back to That Evening

The evening pictured earlier has not arrived yet, and it is unknown whether it will unfold exactly like that. Not a single line has been revealed about what Labs will actually release. However, it is certain that while six variations were being created in that room, no one waited for an installation file and no one went through store reviews. The fact that a document authored by the platform holder—acknowledging their own business model could be shaken—was made public illustrates exactly where this industry stands today.