Browser Games

Browser games run directly in the browser without an install, which shapes how they are built, tested and kept running.

Browser games are played in the browser itself, usually without an install and often without a store in between. That constraint runs through the whole production: builds have to load fast over a normal connection, run on hardware the studio cannot choose, and survive the differences between browser engines. Teams working here tend to use web technology alongside an engine with a web export, and they deal with storage, accounts and payments through the web rather than through a platform holder.

Most browser titles are operated as live services, so the work does not end at release. Updates ship continuously, often several times a week, and a broken build is visible to every player at once rather than to those who downloaded it. Quality assurance therefore covers a matrix of browsers and devices, and economy and progression are tuned against live numbers.

The skill sits close to free-to-play and mobile work, since the same titles frequently ship in both places, and it differs from console development mainly in the absence of certification and in the amount of compatibility testing it demands.

Where these positions are: St. Julian’s (1)

Open positions for Browser Games (1)

All jobs for Browser Games