Real hardware, not an emulator
An emulator renders your page the same way for everyone. A Redmi running MIUI does not render like a Samsung running One UI, and that is often where things break. Declic captures on real devices.
On real phones
Screenshots on a real Android phone, from one HTTP request
You send a URL. A real device opens the page, waits, and you get back the image, the video and the logs. No emulator, no browser farm: real hardware, with its real fonts, its real network and its real bugs.
No credit card to start. Secure payment through Stripe when you change plan.
A real screenshot, taken on the fleet's Redmi.
What it does
Concretely
Everything you need to understand
The response carries the screenshot, the video if you ask for it, the filtered Android log, and the specs of the device that ran it. Enough to reproduce, not just to observe.
An API, never a shell
Declic only exposes actions that can be undone: open a URL, install an APK, run a short sequence. There is no free `adb shell`, not even on a paid plan — that is what keeps a device healthy for the next customer.
Every device starts clean
Between two requests the device is reset. Apps installed by one customer do not spill over into the next.
Emulator or real device
What only breaks on a real phone
An emulator shares your machine: the same fonts, the same WebView, the same network. The fleet's Redmi shares nothing with you — and that is exactly where your bugs live.
On an emulator
- Your workstation's system fonts.
- An AOSP WebView, identical for everyone.
- Your machine's network, stable and fast.
- Memory to spare: nothing is ever killed in the background.
- No manufacturer skin.
On the fleet's Redmi
- The manufacturer's fonts and density, the ones your users see.
- The system WebView, updated by Xiaomi.
- The device's own network, with its latency and its dropouts.
- MIUI kills background processes as soon as memory runs short.
- The skin: navigation, permissions, power management.
Questions
Frequently asked questions
Can I run a free `adb shell`?
No, and it is not a temporary limitation. The API only exposes reversible actions so that a device cannot be left in an unusable state.
How long does a capture take?
About six seconds for a simple page, more if the page is heavy or the queue is busy. Synchronous mode waits up to 60 seconds; otherwise the request runs asynchronously and you receive a signed webhook.
Is there an emulator fallback?
No. If the fleet is busy your request waits. We would rather make you wait than hand you a capture that does not match the hardware you targeted.
Can I pick the network?
Wi-Fi is always available. 4G, 2G and 3G depend on the device: forcing a network is not guaranteed by every manufacturer, and when the measurement does not confirm the change the result says so instead of pretending.
In all honesty
What we do not do
A product that hides its limits wastes everybody's time. Here are ours, today.
- No free shell access, even on a paid plan: only reversible actions are exposed.
- 4G is not available on every plan, and forcing the network is not guaranteed by every manufacturer.
- The fleet is small today: expect a queue at busy times.
- No custom DNS in phase 1.
Try it on a real phone
Create an account, take a key, run your first test. It is free to start.