Real phones. Real control. In your browser.

Tap, swipe, and ship on iOS and Android hardware from one team fleet — no cables on your desk.

phloom · /devices6 of 6

iPhone 14

iOS 17

Pixel 7

Android 14

Galaxy S22

Android 13

iPhone SE

iOS 16

Pixel 6a

Android 14

Galaxy A54

Android 14

ch. 01the drawer

First, the drawer.

Before the fleet, there is a drawer. Every mobile team has one — the place where test hardware goes to be lost.

  • iPhone 14taped to a desk in QA — do not unplug
    claimed
  • Pixel 7in someone's bag since March
    missing
  • Galaxy S22battery swollen, retired but never removed
    retired
  • USB hub nº 4works if you hold the cable just right
    flaky
  • The spreadsheetlast updated by someone who left
    stale

The devices are real. Reaching them is the broken part.

ch. 02the fleet

What is Phloom?

Phloom is a browser-based remote device control platform for teams. QA engineers, developers, and lab operators tap, swipe, and test on provisioned iOS and Android hardware from a shared fleet — with team-scoped access and role-based permissions — without USB cables or per-tester installs.

  • 01.

    Live device control

    Tap, swipe, type, install apps — anything you would do with a phone in your hand, in your browser.

  • 02.

    Multi-OS, multi-team

    iOS, Android, Tizen, webOS — on a shared fleet with per-team isolation and role-based access.

  • 03.

    Managed fleet access

    Accounts and teams are provisioned by your administrator. Sign in, pick a team, and work from one place.

ch. 03the session

Real devices. Real browser. Real time.

A few hundred milliseconds of glass-to-glass latency across your provisioned fleet. Tap a device and you are inside it.

fig. Ione session, in flight.
Instagram
2
Your story
maya_klr
dev.arvid
qa.lab
renny
habchysAoraki / Mount Cook National Park
2,4818754

habchys golden hour on the ridge — no filter

View all 87 comments

2 hours ago

Instagram
2
Your story
maya_klr
dev.arvid
qa.lab
renny
habchysAoraki / Mount Cook National Park
2,4818754

habchys golden hour on the ridge — no filter

View all 87 comments

2 hours ago

Add to story
Recents
0:140:31
Aa
Your storyClose friends

Tap a provisioned phone in your browser; the phone answers.

01.Lowglass-to-glass latency target
02.Browserno client install
03.Teamsscoped device pools
ch. 04the teams

Built for

  • i.Mobile QA Teams

    Run manual checks and automation against real hardware — not just simulators.

  • ii.App Dev Shops

    Share one fleet across designers, developers, and PMs without passing around USB cables.

  • iii.Device Lab Operators

    Centralize provisioning, team assignment, and day-to-day access from a single admin surface.

ch. 05the questions

Frequently asked questions

Straight answers on access, fleets, and fit.

What is Phloom?
Phloom is a browser-based remote device control platform for teams. It lets QA engineers, developers, and lab operators tap, swipe, and test on provisioned iOS and Android hardware from a shared fleet — with team-scoped access and role-based permissions — without USB cables or per-tester client installs.
Who is Phloom for?
Phloom is built for mobile QA teams, app development studios, and device lab operators who need shared access to real hardware. Administrators provision accounts and teams; members sign in and pick a team from the switcher.
How do I get access to Phloom?
Phloom is invite-only. Your administrator creates your account, assigns you to teams, and provisions devices. When you have credentials, sign in at the login page and select your team in the top-bar switcher.
Does Phloom support iOS and Android?
Yes. Phloom supports live control of provisioned iOS and Android devices in the browser. The platform also supports Tizen and webOS hardware in the same fleet model for operators managing multi-OS labs.
Do I need to install software on my computer?
No client install is required for day-to-day device control. You sign in through the browser and stream to assigned devices. Provider hosts run on machines connected to physical hardware; testers only need a modern browser.
How is Phloom different from simulators?
Simulators emulate software environments; Phloom controls physical devices with real radios, cameras, and OS builds. Teams use Phloom when hardware fidelity matters — mobile QA, device-specific bugs, and fleet-wide manual or automated testing.
Can teams share a device fleet?
Yes. Phloom uses team-scoped device pools with role-based permissions. Each team sees only its assigned devices, while administrators manage inventory, provider hosts, and assignments from admin surfaces.
Does Phloom support automation or Appium?
Phloom integrates with automation workflows including Appium sessions and custom action scripts. Teams can build script libraries, run actions against devices, and tail Appium logs from admin surfaces without SSH.
ch. 06the invitation

Access is by invitation

Your administrator creates accounts, assigns teams, and provisions devices. When you have credentials, sign in and select your team.

fig. IIthree steps, then you are in.
  1. 01.Receive your username from an administrator
  2. 02.Sign in with your credentials
  3. 03.Pick your team in the top-bar switcher
Sign in
  • Team-scoped device pools
  • Role-based permissions
  • One browser tab for the whole fleet