15-Year-Old Developer Gets Doom Running Through App Customization Features, Without Changing the Main App

Bennett Schwartz, a 15-year-old developer, posted a video on X. In the video, Doom runs inside an app's interface. His exact words were: “Don't worry, it can run Doom.” Apart from customization features, he did not need to modify the app itself.

The tweet was retweeted by Mario Zechner. The noteworthy part is the second half: the app was not modified. Doom has a long porting history, from calculators to cameras to all sorts of strange devices, and the community often uses it as a portability test. David Stark said in a reply that Doom is the Turing test for any app. That claim is a bit exaggerated, but it is very apt here: the fact that it runs shows that at least one layer of the app's extension points, input/output, and rendering path is open enough.

Pronsh's question is more practical: wouldn't input go into the text box? How do you control it? The video does not explain. Bennett also did not go into technical details. Judging from “only touching customization features,” Doom most likely ran by leveraging the app's customization capabilities, while input mapping and display rendering would need separate handling. The materials do not show exactly how it was implemented, so we cannot guess.

Mad Hatter chimed in: Can it run Crysis? This is an old meme, and it also reminds people not to treat Doom as the only standard. Just because Doom runs does not mean the app is open enough to run modern 3D games. It is more like a low-cost signal: this app's boundaries are wider than the documentation suggests.

For AI practitioners, what is worth looking at in this tweet is the extension points and constraints. For ordinary users, it is like a familiar old game suddenly appearing in an unfamiliar place. Put the two together, and that is enough to make it spread.