Skip to content
ZekaForge
Product

How remote device testing works

The architecture behind browser-based access to real Android devices — and why EC2 alone is not enough.

Remote device testing feels simple — a phone on your screen — but a few moving parts make it work.

The pieces

  • Device workers: hosts physically connected to Android devices, running the Android Debug Bridge (ADB).
  • Streaming gateway: a secure service that streams the screen (via WebRTC) and relays your input back to the device.
  • Orchestration: reserves devices, enforces quotas and concurrency, and cleans sessions up when they expire.
  • Object storage: Amazon S3 holds APKs and recordings, with lifecycle rules to control cost.
  • Queues: Redis-backed jobs run automated tests and post-processing in the background.

Important reality check

A plain EC2 instance does not come with a physical phone attached. Real device access requires either connected hardware (a device-worker fleet) or a managed service such as AWS Device Farm, which offers remote-access sessions on real devices.

Demo mode

When no hardware or managed service is configured, ZekaForge runs a labeled demonstration mode behind the same interface, so the product and APIs can be built and reviewed end-to-end before devices are wired in.

مشاركة

مقالات ذات صلة

ابدأ مع ZekaForge

أنشئ حسابًا مجانيًا واكتشف Device Cloud وCyber AI خلال دقائق.