Core terms behind cloud phone operations
Glossary pages define the concepts that keep appearing across product, compare, and guide pages so users can align vocabulary before deeper evaluation.
What the glossary layer is supposed to do
Four terms users usually need first
What Is a Cloud Phone?
Define the core concept and explain how cloud phones differ from emulators and browser-only environments.
What Is a Cloud Emulator?
Explain where cloud emulators fit, how they differ from local emulators, and why teams may choose cloud phones instead.
What Is a Proxy Browser?
Clarify where proxy browsers fit and where they stop compared with cloud phone execution.
What Is a Multi-Account Browser?
Explain how browser-based account separation differs from mobile device-level operations.
Why this layer matters
It removes vocabulary drift
Users often search adjacent terms with overlapping intent. The glossary layer keeps those terms from collapsing into one vague story.
It sets up the product story
A clear definition makes it easier to understand why cloud phone pages and compare pages are structured the way they are.
It keeps users moving
Use the glossary to understand a term quickly, then move into the product or comparison path that matches your next question.