Fifteen years of right-clicks: what RuneScape's mobile port actually cost

The expensive item on that audit list is not the hard-coded screen dimension. That one is findable and mechanical. The costly one is the right-click.

RuneScape's desktop model put a context menu behind nearly every object in the world: talk to an NPC, pick up an item, examine it, attack it ^[9]. Hover states let a player preview information before committing to a click ^[10]. A mouse hands you two independent channels for free, plus pixel precision. A finger gives you one contact point, no preview, and a contact patch wider than several of the elements it has to hit. So every interaction that used to open a menu becomes a question about what a single tap should default to, and the reasoning behind the original refusal to pick a default is not in a document you can search, because much of the code was written by people who had already left the company, in patterns that predate current convention ^[5].

The panels repeat the problem at a different scale. Inventory, equipment, prayer, magic and combat stats were all on screen at once on desktop ^[11]. Hiding most of them is the obvious answer and also the one the audience notices, because the community arrived with firm expectations about how the game should look and feel ^[13].

The memory figures set the outer bound. Desktop rendering paths assumed a floor of 2GB or more of available RAM, while mobile devices were often limited to 1-2GB in total, shared with the operating system ^[7]. At the bottom of that range, the desktop floor alone is twice the whole device budget before the OS takes its share ^[2]. Since both clients sit on one persistent world with one player-driven economy ^[12], the savings cannot come from carrying less world. They have to come out of how the same world is represented.

Two numbers deserve care. The publisher's headline sells a 20-year-old game, and the article's own inventory cites over 20 years of content from hundreds of developers ^[17], while the same piece dates the codebase at more than 15 years when the author joined ^[3] and puts his tenure at 2017 to 2019 ^[2]. Measured from the 2001 release ^[1], the codebase was roughly 16 years old when he started ^[1]. The 20 is the game's age at the time of writing, not the age of the thing being ported. The account is also single-sourced: a former employee, writing afterwards, whose current studio sells the audit-first method it describes and has applied it to remaking Nub ^[15][16]. The claim that weeks of audit saved months of production is his estimate ^[8], and Jagex is not represented in the piece.

What transfers is the order of operations rather than the checklist. Settle the scope boundary first, since a parity client and a companion app price out as different projects ^[18], then write down every service the old platform was quietly providing: fixed screen geometry, pointer precision, hover, memory headroom, and the assumption that you are the only client touching the world ^[6][4]. Code comes after that. Anything on the list nobody wrote down arrives later as a production incident with a ship date attached ^[8].