How to Report an App's Apple Silicon Compatibility on Does It ARM

Updated

To report an app's Apple Silicon compatibility on Does It ARM, use the Request an App link in the site footer, which opens a GitHub-based submission. Include the app name and the version where you observed native support, Rosetta use, or failure. Your report then feeds into the site's status labels and "reported as of" version and date, which is why entries on the list show lines like "Native Apple Silicon Support reported as of v2.6.12."

Before You Submit

  • Confirm the app is missing or outdated. Search the compatibility list first. If the app already appears but shows an older version than the one you tested, a report still helps update it.
  • Know what you observed. The site's labels are specific: ✅ Native, ✳️ Rosetta, ⏹ In Progress, 🚫 Unsupported, and 🔶 Unreported. Pick the one that matches your actual result rather than guessing.
  • Note the version number. The list ties each report to a version, so an exact number (e.g., v2.6.12) is more useful than "latest."
  • Have a GitHub account ready. The submission path runs through GitHub, so you'll need to be signed in there.

Step-by-Step

  1. Go to doesitarm.com and scroll to the footer.
  2. Select Request an App with Github. This is the site's contribution entry point for apps that aren't listed or need an update.
  3. On the GitHub side, identify the app clearly — its name and, if helpful, the developer or bundle identifier so it isn't confused with a similarly named app.
  4. State the version you tested and the result: native support, running under Rosetta, in progress, or not working.
  5. Add any detail that helps others judge the report — for example, whether the app launched normally, whether it prompted to install Rosetta, or whether specific features failed.
  6. Submit and wait for the maintainers to review. The site describes itself as community-built ("Built by Sam Carlton and the awesome Does It ARM Contributors"), so updates appear as reports are processed.

What Happens to Your Report

Your submission becomes part of the same dataset that drives the site's summary figures. The homepage currently shows 3,688 listed apps, with 57.6% native, 7% Rosetta, 34% needing info, and 1.4% unsupported. Each entry also carries a recency marker — "7 days ago," "last month" — so a fresh report both changes a status and refreshes how current that app looks.

A concrete example of why version matters: SSH Config Editor is listed as native "as of v2.6.12," while MacPass is native "as of v0.8.2." If you tested a newer build of either and it still works natively, your report extends that version reference; if it broke, the status may need to change.

Common Snags

  • Submitting a duplicate. Check the list and its pagination ("Next →") before filing; the app may be on a later page.
  • Vague version info. "Newest version" ages badly. A number stays checkable.
  • Reporting an unreported app as unsupported. 🔶 Unreported means no one has confirmed either way — only mark 🚫 Unsupported if you actually saw it fail.
  • Expecting instant updates. Contributions are community-driven, so there can be a lag between submission and the list reflecting it.

When This Isn't the Right Route

If you only want to check compatibility rather than report it, the list itself and its category, device, benchmark, and game pages are the faster path. The Scan Apps option on the site is aimed at checking your installed apps rather than filing a single report. Use the GitHub request route when your goal is specifically to add or correct an entry.