Social on cloud. Neo-banks on physical.

What "Cloud OK" and "Physical recommended" actually mean

Our compatibility labels are honest operating guidance, not marketing. Cloud OK means the app runs as a production client on a remote Android seat — you can warm it, keep it open, and operate it at scale from the cloud. Physical recommended means the app's own defenses make a physical handset the safer home, and putting it on a cloud seat is fighting the app rather than using it.

The dividing line is roughly this: apps that mainly care about content and behavior sit comfortably on cloud; apps that run hardware attestation, aggressive anti-fraud, or device-integrity checks tied to real handset signals push toward physical. We'd rather tell you "use a phone for this one" than sell you a seat that quietly fails a KYC step two weeks in. See cloud devices and physical devices for the two homes.

Social and messaging apps run on cloud

The social stack is the core cloud workload — it's what the platform is built and tuned for:

• Snapchat — the flagship, and the hard case; if a cloud phone can run Snap as a production social client, the rest of the stack is comfortable. Details on the Snapchat page.
• TikTok — content and multi-account operations run well on cloud seats. See TikTok.
• Instagram — social-first seats handle IG multi-account with per-seat proxies. See Instagram.
• WhatsApp and Telegram — messaging works on cloud; the practical constraint is SMS verification, which you plan for with the right number and proxy, not the seat itself.

Across all of these the same discipline applies: one account per seat, one sticky proxy persona per seat, human warm-up before any automation.

Why neo-banks and some banking apps prefer physical

Neo-banks and many banking apps are the clearest "physical recommended" category, and it's not a limitation of the cloud — it's the apps doing their job. Fintech onboarding leans on device attestation, hardware-backed integrity signals, and anti-fraud systems that specifically look for signs of a virtualized or remote environment. A KYC flow is exactly where those checks bite hardest.

Parking a neo-bank on a cloud seat means you can pass a casual open and then fail at the moment that matters — identity verification, a card provisioning step, or a fraud review. We steer fintech to physical handsets as a matter of honesty, not caution for its own sake. It's also good hygiene: you never want a bank's KYC identity sharing a device with a social automation seat. See the neo-banks page for the full reasoning.

How to decide, app by app

You don't need a compatibility matrix memorized — you need three questions per app:

1. What does this app defend? Content and behavior → cloud is fine. Money, identity, and hardware attestation → lean physical.
2. What happens at the strictest step? Think past the first open to the moment of truth — a KYC check, a card link, a payout. If that step inspects the device deeply, put the app where it expects to be.
3. How much is the account worth, and how many do you need? High-volume social multi-account is a cloud problem. A single high-trust financial identity is a physical problem.

When in doubt, prove it on a cheap Spark seat before you commit real accounts. A $9 test that fails early is far cheaper than a warmed identity that dies at verification.

Snapchat is the acid test

If you only benchmark one app to judge a cloud phone, make it Snapchat. Snap is unusually sensitive to environment integrity, which is exactly why so many generic "Android in the cloud" hosts quietly fail it while claiming "all apps supported." A host that can run Snap as a production, multi-account social client under isolation, stable identity, and a clean mobile proxy has cleared a bar that makes TikTok, Instagram, and messaging look easy.

That's why we treat Snap as first-class rather than a footnote — it's the honest stress test for the whole cloud stack. If a vendor won't say the word "Snapchat" or buries it under "try a physical device," that tells you their cloud can't clear the bar. Read the full breakdown on the Snapchat page, and if you're weighing environments, the cloud vs emulator guide.