First, identify your MacBook Air
The MacBook Air name spans multiple generations. Open the Apple menu and choose About This Mac. Note the model, chip or processor, memory and macOS version. Those details are more useful than the laptop’s color or screen size when checking a game’s requirements.
Apple-silicon Macs show a chip name; Intel Macs show a processor. Apple’s Apple-silicon identification guide explains the distinction. Do not publish your serial number when asking for help.
Check the current store requirements
Open the Mars47 App Store listing on your Mac and inspect its Mac compatibility information. Requirements can change between versions, and a web listing can show information for more than one platform. The listing presented to your own Mac is the right place to check before downloading.
Check the supported macOS version and any hardware requirement together. Make sure you also have room for the download and installation. Use the requirements shown for the available version rather than a rule of thumb based on the MacBook Air name.
Compatibility answers whether a version can be installed. It does not promise identical performance across an early base, a developed industrial area and a busy launch scene.
What kind of space strategy are you getting?
Mars47 puts you in charge of a coastal spaceport. You plan infrastructure, connect roads and supply the staff and power behind research and missions. The attraction is the program that makes a launch possible: a sequence of grounded decisions rather than simply a flight across the sky.
That matters when choosing a laptop game. If you enjoy inspecting a layout and deciding which dependency to fix next, watch the official gameplay showcase. If you want a broader comparison of exploration, tactics and program management, start with space games for Mac.
A useful first-session check
- Note the version and your Mac model. Keep these together if you later report a problem.
- Start with an ordinary campaign. Inspect road placement, camera movement and the readability of the mission panel.
- Try the scenes you care about. A quiet opening plot is not equivalent to a developed base.
- Change one condition at a time. Compare the same view after closing a demanding background task or disconnecting an external display.
- Save before experimenting. Keep your campaign progress while investigating a display or performance issue.
Use the display and graphics options actually offered by your installed version. If you compare display modes, keep the same scene visible so you can judge the effect of the change.
If performance feels uneven
Describe the symptom precisely. A delayed button response, uneven camera motion and a slow simulation are different observations. Note whether it happens in one location, after the base grows, or while another application is doing heavy work.
For a repeatable comparison, keep the same save, camera position and display arrangement. Change only one condition, then return to the same view. A single momentary improvement does not establish a reliable settings recommendation.
We have not yet published model-by-model MacBook Air benchmarks. A screenshot demonstrates the scene, while a useful performance result also needs the exact hardware, game version, display setup and test conditions. If you need help, use the contact form with your model, memory, macOS and game version, plus the steps that reproduce the issue.
Start with a working base
Once compatibility is confirmed, the beginner tutorial takes you through the opening infrastructure. Learn the mission panel and road access before expanding. Keep an eye on money, power and people, then build the facility that removes the next constraint.
You can also read about the Godot development work behind Mars47. That article explains the project workflow; it is separate from the device-specific performance evidence you should use when evaluating your own laptop.