Product engineering · evidence before claims

Can push-to-talk work over satellite-to-cell?

Technically, brief low-bitrate push-to-talk is a promising match for constrained satellite data. Commercially and operationally, it works only after the carrier admits the app and real hardware proves the connection time, latency and continuity are good enough.

CRAGGEN's status today

The Android app is prepared for constrained satellite networks. No carrier has approved CRAGGEN and no satellite-to-cell field test has been completed. It works over ordinary mobile data and Wi-Fi now; we do not describe satellite operation as live.

Push-to-talk sends brief voice bursts instead of a continuous group callA timeline compares continuous call traffic with three short push-to-talk transmissions separated by listening time. SAME TEN-MINUTE WINDOW · DIFFERENT TRAFFIC SHAPE GROUP CALLCONTINUOUS AUDIO PATH PUSH-TO-TALK TALKTALKTALK LISTENLISTENLISTENTIME LESS DATA IS HELPFUL · CARRIER APPROVAL AND LINK CONTINUITY STILL DECIDE WHETHER IT WORKS
FIG 1 · Push-to-talk is naturally bursty, but a small payload cannot cure an unavailable or interrupted link.

Why push-to-talk is a credible fit

A group call keeps two-way audio paths open and mixes several voices. Push-to-talk sends one person's voice only while the control is held. Everyone else listens. That reduces simultaneous traffic and makes the usage pattern naturally bursty.

One speaker

Only the active talker transmits audio, avoiding a many-person conference mix.

Brief bursts

Operational messages tend to be short: status, direction, confirmation and warning.

Low bitrate

CRAGGEN uses the Opus voice codec at roughly 16 kbps on supported Android versions.

No stored audio

The relay forwards live traffic; it is not a server-side voice archive.

Those characteristics reduce the amount of data. They do not eliminate satellite delay, satellite handovers, obstruction, network admission or congestion.

What Android support actually means

Android lets a compatible app declare that it is optimised for satellite data and ask the operating system for bandwidth-constrained networks. CRAGGEN includes the satellite optimisation property and explicitly requests constrained networks.

This matters because an app that never asks for an eligible constrained network may remain offline even when the phone has a satellite data path. It also encourages disciplined app behaviour: small transfers, fewer background requests, graceful pauses and clear state.

It is still not a carrier bypass. The network can allow selected apps only. Android preparation answers “can the app behave appropriately?”; the carrier still answers “may this app use our service?” Read the official Android constrained-network guidance.

The four gates before a satellite claim

  1. App preparation. Low-bitrate audio, constrained-network support, reconnection logic and honest UI state.
  2. Carrier admission. The app must appear on the network's approved list or be included in a controlled trial.
  3. Hardware field test. Use an eligible phone, plan and carrier outside terrestrial coverage with clear sky.
  4. Measured acceptance. Record connection time, first-audio delay, drop-outs, talk-burst success, satellite handover behaviour and battery impact.

CRAGGEN has passed the first gate. The remaining three are visible on our carrier-sourced satellite status tracker.

What the user experience must handle

A premium interface cannot pretend every data path behaves like 5G. If satellite testing opens, the app must describe the state a user can act on:

StateUseful interface messageWhat the user should do
SearchingLooking for a usable networkMove outdoors and keep a clear view of the sky.
Connected but constrainedConstrained connection · short messages work bestKeep talk bursts brief and wait for confirmation.
ReconnectingConnection paused · your audio was not sentDo not assume the channel heard the message; retry when ready.
UnsupportedThis carrier does not currently allow CRAGGEN over satelliteUse terrestrial data or the planned fallback equipment.

The most important product rule is that the UI must never imply a transmission succeeded merely because the user pressed the button. Observable state, audible confirmation and explicit failure are more valuable than optimistic animation.

Where live app voice already proves something

O2 Satellite in the UK, Rogers Satellite in Canada and One NZ publish support for selected app-based calling or communications. That demonstrates that low-bitrate live app voice can cross some direct-to-cell services. It does not prove CRAGGEN is admitted or that a one-to-many push-to-talk session will meet its usability target.

See the live carrier table for the current evidence and the O2 eligibility guide for the UK app gate.

What satellite push-to-talk should not replace

Use radio for local voice when the operation cannot depend on an external network. Use appropriate specialist satellite or distress equipment when remote safety depends on raising help. A phone app can become an excellent additional layer; it should not be framed as the only layer where failure has serious consequences.

Our equipment comparison starts with the consequence of failure, while the no-signal guide covers the gaps no app can honestly erase.

Public test promise

When a carrier trial becomes available, we will record the country, carrier, phone, software, plan, sky conditions and measured results. Until then, the correct public status remains “technically prepared, not approved or field-proven”.

Use the same simple habit today

Join a private channel, hold to talk, release to listen. CRAGGEN works over mobile data and Wi-Fi now, including with the screen off.

No account · no tracking in the app · no server audio recording · joining is free