MAC APP SECURITY

Mac App Store vs Direct Downloads: Security Explained

Know where an app comes from, what has been checked, and what access it needs.

Can an app outside the App Store be safe to use?

Direct distribution is an established macOS distribution route. A Developer ID signed, notarized app can pass Apple’s security checks without being sold in the Mac App Store. The checks differ, so consider the download source, permissions, data handling and updates as well as where the app is listed.

Which apps can be in the Mac App Store?

The store includes many kinds of software, from writing and design tools to games and utilities. Developers submit apps for review against Apple’s rules covering areas such as safety, functionality, privacy and business practices. It is a distribution channel with acceptance requirements, rather than a list of every legitimate Mac app.

For Mac apps, the App Review Guidelines include App Sandbox and public-API requirements. App Sandbox restricts access to resources and other apps, with specific capabilities granted for supported needs. This provides an additional boundary around what an app can do.

The store also provides a common route for installation and updates. Apple describes it as the safest place to get Mac apps in its safe-installation guidance. Review and sandboxing are meaningful protections; they are not a promise that every app will always be free of bugs or security vulnerabilities.

What changes outside the store?

A developer can distribute a Mac app from a website and provide its own update and purchase arrangements. Reasons vary: the app’s technical needs, distribution model or business choices. Absence from the store, by itself, does not tell you whether an app was rejected, is trustworthy, or handles data responsibly.

macOS still has protections for downloaded software. Apple’s Gatekeeper documentation describes checks of developer identity, integrity and notarization for software opened from outside the App Store.

  • Developer ID signing: helps establish the app’s developer identity and detect changes to the signed software.
  • Notarization: Apple’s automated service checks submitted software for malicious content and code-signing issues.
  • App Review: the separate review process for distribution through the App Store.

Apple explicitly distinguishes notarization from App Review. A notarization ticket does not certify every feature, promise permanent safety or guarantee the developer’s privacy statements. Directly distributed apps may also have different sandbox arrangements; signing and notarization do not imply App Sandbox is enabled.

Permissions deserve their own decision.

A trusted download source does not make every permission request necessary. Check whether the requested access has a clear connection to the feature you want. For a window switcher, controlling another app’s window and capturing a preview serve different purposes.

macOS lets you review or revoke Accessibility access and screen-recording access in System Settings → Privacy & Security. These permissions are powerful. An explanation of how the app uses them should be part of your decision.

How StillSwitch approaches that responsibility.

Security and privacy are part of StillSwitch’s design and release process. The current official release is Developer ID signed and Apple notarized; its signature, attached notarization ticket and Gatekeeper assessment were checked for this article.

StillSwitch is distributed outside App Sandbox because of the cross-app window control its implementation uses. That carries responsibility: it does not have the same sandbox boundary required of Mac App Store apps. The distribution article explains the technical decision, including its non-public window-control APIs and compatibility implications.

  • Local window processing: preview snapshots stay in memory. StillSwitch does not save them as screenshot files or upload them.
  • No app analytics: the Mac app does not report which apps you use, which windows you select, or how often you switch.
  • Optional previews: Screen Recording access enables preview snapshots. Without it, the switcher can use app icons; Accessibility and keyboard access are still needed for switching.
  • Signed updates: the built-in updater checks signed updates delivered over HTTPS.

Licensing and updates make network requests. Local processing does not mean the app never connects to the internet. Read App privacy & security for the full explanation of permissions, local records and those connections. Website analytics are described separately.

These are concrete safeguards and data boundaries. They are not a claim that any software can be completely risk-free or that notarization replaces an independent security audit.

Before opening a direct download.

  1. Start at the official source. For StillSwitch, use the Download control on stillswitch.app or the Homebrew command in the setup guide.
  2. Read the macOS message. A first-open confirmation for an internet download differs from a warning about malware, an unverifiable developer or damaged software. Apple explains these messages in its installation guide.
  3. Keep security checks enabled. StillSwitch’s installation instructions do not require disabling Gatekeeper or System Integrity Protection. If a security check fails, stop and use the support information rather than bypassing it.
  4. Review access and keep updates current. Grant permissions for features you want, and follow your organization’s software policy on a managed Mac.

Choose the distribution route and permissions you are comfortable with. StillSwitch makes its route, safeguards and data handling explicit so you can make that decision before installing.

Written by the maker of StillSwitch. Apple references and the official StillSwitch release reviewed on . This explains the current safeguards, not a guarantee against every security risk.

Download for Mac Setup, trial & requirements

14 days free. No card. Apple Silicon and macOS 15 or later.