Every device, in bloom.

Real iOS and Android hardware, streamed live to your browser. Tap, swipe, and ship from one shared fleet. No cables, no drawer.

See it work
Sign in
Scroll to explore
fig. 0the live device cockpit.

iPhone 15 Pro

Apple iPhone 15 Pro · iOS 18.2

Plugged in

Live video

WebRTC · auto quality

60 fps

Read-only stream connected. Take control to send input.

where devices fall out of reach

First, the drawer.

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

hardware, cables & lost time
  • iPhone 14claimed

    taped to a desk in QA; do not unplug

  • Pixel 7missing

    in someone's bag since March

  • Galaxy S22retired

    battery swollen, retired but never removed

  • USB hub nº 4flaky

    works if you hold the cable just right

  • device inventory final v7
    The spreadsheetstale

    last updated by someone who left

mobile lab · miscellaneous

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

one fleet, ready to use

Then, the fleet.

Phloom replaces the drawer with provisioned devices that are ready for every teammate allowed to reach them.

provisioned hardware, in rows
the atlas entry

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. No USB cables or per-tester installs required.

  • Live device control

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

    reach any device

  • Multi-OS, multi-team

    Use iOS and Android devices on a shared fleet with per-team isolation and role-based access.

    iOS and Android together

  • Managed fleet access

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

    managed access by team

control in real time

The session, live.

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. 1a real session, posting a story
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
Low
glass-to-glass latency target
Browser
no client install
Teams
scoped device pools
teams and access

Built for the work.

fig. 2built for
fig. 3managed access

Access is by invitation

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

  1. provision01

    Receive your username from an administrator

  2. assign02

    Sign in with your credentials

  3. control03

    Pick your team in the top-bar switcher

Team-scoped device poolsRole-based permissionsOne browser tab for the whole fleet
questions from the field

Field Notes.

Note 01
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. No USB cables or per-tester client installs required.
Note 02
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.
Note 03
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.
Note 04
Does Phloom support iOS and Android?
Yes. Phloom supports live control of provisioned iOS and Android devices in the browser. Teams can manage both platforms in the same fleet model with shared access, team isolation, and role-based permissions.
Note 05
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.
Note 06
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 for mobile QA, device-specific bugs, and fleet-wide manual or automated testing.
Note 07
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.
Note 08
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.

Bring your fleet online.

One browser tab between your team and every device it is allowed to touch.

invite-only · accounts are created by administrators