iOS: Official App Store Listing Is a Real Plus
SakuraCat's iOS client supports iOS 12.0 and above, distributed officially through the App Store – worth noting, since many comparable Chinese-market acceleration services rely on direct web installs or enterprise-certificate signing, both less stable and less durable than an App Store listing. The site also mentions iOS Widget support, letting users check connection status or connect with one tap from the home screen – a nice touch of attention to detail.
iOS Platform Limitations
Like nearly every iOS VPN or proxy app, SakuraCat is constrained by Apple's Network Extension framework: it can't implement Android-style per-app split tunneling, and any kill switch behavior can only be approximated through iOS's "On Demand" connection rules. These aren't SakuraCat-specific shortcomings – they're platform-wide restrictions Apple applies to all third-party VPN-category apps.
macOS: Native Design and Apple Silicon Support
The macOS client supports macOS 10.12 and above, with the site specifically calling out a "native macOS design," menu-bar quick access, and support for M1/M2 chips – meaning it runs without relying on Rosetta translation on newer Apple Silicon Macs, which should mean better performance and battery efficiency. This is an easy-to-overlook but genuinely practical detail; a number of smaller providers still ship Intel-only-optimized macOS clients, so SakuraCat is reasonably current here.
The Shared Shortcoming Across Both
Neither the iOS nor macOS client discloses the specific tunneling/proxy protocol in use, and there's no third-party audit to cross-check the no-logs claim. If protocol detail and audit history matter to you, both platforms carry the same transparency gap as Windows and Android – a shortcoming across the whole product line rather than something specific to one platform.
What Apple's Rules Mean in Practice
A lot of what feels like a SakuraCat limitation on iOS is actually a platform-wide restriction every VPN and proxy app faces under Apple's Network Extension framework, per the IP security architecture standards most tunneling implementations build on:
| Capability | Available on iOS | Available on macOS |
|---|---|---|
| Per-app split tunneling | No – blocked by Apple's framework | Depends on client implementation; not documented here |
| True system kill switch | Approximated via "On Demand" rules only | More feasible at the OS level, but not confirmed for this client |
| Background reconnect | Subject to iOS background-execution limits | Generally more reliable than mobile OSes |
| Widget / quick toggle | Yes – confirmed on SakuraCat's iOS app | Menu-bar quick access confirmed |
Practical Tips for Apple Users
- On macOS, check Little Snitch or the built-in firewall logs if you want extra visibility into what the client is actually doing – SakuraCat doesn't publish this itself
- On iOS, don't rely on "On Demand" rules as a true kill switch for sensitive traffic; treat it as a convenience feature, not a security guarantee
- If you use both an iPhone and a Mac, test node selection independently on each – node performance can vary by device and network even under the same account
- Apple Silicon Macs should confirm the app is running natively (Activity Monitor's "Kind" column) rather than under Rosetta, to get the performance benefit SakuraCat advertises
iOS / macOS Verdict
The Apple ecosystem is arguably SakuraCat's most polished platform pairing: an official App Store iOS app with Widget support, and a macOS client that's native to Apple Silicon. If you primarily use an iPhone, iPad, or Mac, this should be the smoothest experience of the four platforms – though the protocol-transparency and audit gaps described elsewhere in this review still apply.