Boosteroid on a Mac: playing in a window with nothing else

Searching for "boosteroid mac" produces two answers at once, and they pull in opposite directions. The official download page lists a macOS client, in two builds. The marketing on the front page says no downloads are needed and the whole thing plays in a browser. Both statements are true, and the decision between them is the actual question, because a cloud gaming session in a browser tab behaves very differently from one in a window of its own.

This is worth getting right before a controller is even plugged in. In cloud gaming, the browser is not a viewer. It is the input layer, and every keystroke it intercepts is a keystroke the game does not receive.

What the downloads page actually lists for macOS

The Mac section of the official downloads page is split in two, by processor generation. There is a build for Intel Macs with a stated requirement of macOS 10.13.6 or newer, and a separate build for Apple silicon, listed as macOS 11 or newer. Windows gets both an installer and a portable build, and Linux gets deb, rpm and portable options. Mobile covers Android 8 and above, with iOS handled through a web shortcut rather than an App Store app.

That last detail is the tell. The iOS instructions on the same page describe opening the site in Safari, using the share button and choosing Add to Home Screen:

Make sure you use Safari browser. Tap the Share button on the tool bar. Swipe up and select Add to home Screen from the menu. Source: boosteroid.com

In other words, on the platform where a native client is not an option, the answer is a web page given its own icon and its own frame. That is the same idea a Mac user can apply deliberately, and for a reason that has nothing to do with App Store rules.

Why the browser route is the one that needs help

The service compatibility table on the front page marks Apple devices as supported through both browser and app, and the platform advantages are stated plainly: no game files to download, no updates to manage, no session time limits, and the ability to start on one device and continue on another. Support is listed as 24/7 chat. None of that depends on which route is chosen.

What does depend on the route is input handling. A game running inside a browser tab shares the keyboard with the browser. Command plus W closes the tab. Command plus T opens a new one. Function keys, the Escape key and anything the browser has claimed for itself arrive at the browser first. Full screen mode helps, and it does not eliminate the problem, because the browser is still the process deciding what gets forwarded.

Two more things sit in the way. Notifications from every other tab in the window keep arriving during a session. And the tab itself is one of twenty, which means finding it is a task, and closing the wrong one is a live risk during a queue wait.

The native client removes all of that by not being a browser. When it is available and installed, it is the better route, and there is little reason to argue with it.

When the native client is not the answer

There are cases where the browser is the only door, or the preferable one.

A Mac still on macOS 10.13.5 or earlier falls below the stated floor for the Intel build. A managed or school owned Mac may not allow installing applications at all. Some people simply prefer not to add a background application for something used twice a week. And there is a practical reason that comes up often: the account page, the game catalogue, the subscription and the support chat are all web pages regardless of which route is used for play, so a browser session is part of the workflow either way.

For every one of those cases the choice is not client versus browser. It is browser tab versus a browser window that belongs to this and nothing else, and those are not the same thing.

The three routes, side by side

Route	Needs an install	Keyboard shared with browser	Own Dock icon	macOS floor
Native client	Yes	No	Yes	10.13.6 Intel, 11 Apple silicon
Ordinary browser tab	No	Yes	No	Whatever the browser requires
Standalone window from a site to app tool	Small one time setup	No other tabs to share with	Yes	12 or later

The third row needs explaining, because it looks like a compromise and is closer to a different category. A tool that turns a website into a standalone Mac app points an installed browser engine at one URL and gives it a window with no tab bar and no address bar. The page is identical. The frame is not. There are no sibling tabs to steal a keystroke, no tab to close by accident, and a Dock icon that launches straight into the session.

It also does something the native client does not. The login session is stored in a profile belonging to that app alone, which matters for anyone who shares a Mac or keeps a second account.

What the isolated profile changes in practice

Per app profile isolation means cookies and sign in state do not leak between apps or into the main browser. Three consequences follow.

A shared family Mac stops needing a sign out and sign in dance between sessions, because each person's app holds its own login. A second account stays permanently signed in alongside the first. And clearing the main browser's cookies for an unrelated reason no longer logs the session out.

The browser engine itself is chosen per app. Chrome, Brave, Edge, Chromium, Vivaldi and Opera are all available as engines, and the app links to the installed browser rather than bundling a frozen copy, so browser updates carry through automatically. That last point is what separates this generation of tools from the old wrappers that slowly stopped rendering modern sites. The Guide covers the per app settings that decide the engine, the tab bar, notifications and how the window behaves on close.

Extensions from the Chrome Web Store load into these apps as well, which is occasionally useful and occasionally a trap. Anything that injects into pages costs a little performance, and a cloud gaming window is the wrong place to spend it. Keeping that particular app extension free is the sensible default.

The network decides more than the window does

Before spending effort on windows, it is worth being honest about where the biggest variable sits. Cloud gaming sends input up and video down continuously, so the connection quality between the Mac and the nearest server sets the ceiling for everything else. No frame, native or wrapped, improves a congested link.

Three checks matter more than any software choice. A wired connection removes the largest source of jitter on a Mac that can take one, and on a laptop a wired adapter is often the single biggest improvement available. Sitting on the 5 GHz band rather than 2.4 GHz matters next, because the crowded band is where interference lives. And the number of other devices streaming at the same time matters third, since the service is competing with them for the same upstream and downstream capacity.

The service itself removes several variables that a local install would introduce. Games run on remote hardware, so there are no local game files, no patch downloads and no storage to manage. Sessions are not time limited, and access is immediate when servers are free with queueing during busy hours. A session can also be started on one device and continued on another, which is the reason the account state matters more than the machine.

What that adds up to is a division of labour. The connection decides whether the session is playable. The window decides whether the session is pleasant and whether a stray keystroke can end it. Both are worth fixing, in that order.

Deciding which sites earn their own icon

Wrapping one site raises an obvious next question, and the honest answer is that most sites do not deserve it. A Dock full of icons is the same problem as a browser full of tabs, moved somewhere less convenient.

The test that holds up is frequency multiplied by focus. A site visited constantly but glanced at, such as a search engine or a reference page, belongs in the browser. A site that demands the whole screen and the whole keyboard while it is open belongs in its own window, even if it is only opened twice a week.

Cloud gaming is squarely in the second group. So is a web based video editor, a digital audio workstation, a design tool, and an administrative console for something running in production. All of them want the keyboard and none of them want neighbours. A chat service used all day is a borderline case that usually wins on notifications alone, since a window that can be left open without twenty other tabs behind it is a different experience from a tab.

Applied honestly, the test tends to produce three or four apps rather than fifteen. That is also why the free tier of tools in this category limits the number of apps rather than the features: the limit lands above what most people actually need.

What this costs on top of the subscription

The service publishes its own pricing on the front page, starting from 7.49 euro per month on an annual subscription, with a higher Ultra Pro tier shown from 11.22 euro per month against a 16.89 euro reference price. Those numbers are the service, not the window.

For the window, the free tier of tools in this category covers three apps with all features available, and unlimited apps is a one time 24.99 US dollar upgrade rather than a recurring charge. The stated system requirement is macOS 12 or later, which is higher than the floor for the native client, so a Mac kept on an older release should use the native client instead. The Pricing section spells out both tiers, and three apps is enough for most people to never reach the paid one.

Before building anything by hand, it is worth checking the Supported services list, since several hundred common services ship as presets with the icon and URL already filled in. A service that is not on the list is still buildable from a plain URL in about a minute.

What to change first

Install the native client if the Mac meets the stated floor, because nothing in a browser beats not being in a browser. If installing is not possible or not wanted, stop playing in a shared browser window and give the session a window of its own instead. Kagemusha builds that window from a URL, and the free tier covers three apps.