Pushytap logoPushytap™
Contact Sales

Pushytap NEO · Embedded push-to-talk infrastructure

Pushytap NEO

Put push-to-talk inside your app.

Give workers a way to speak to their team from the software they already use. Flutter, Kotlin and TypeScript SDKs connect your app to NEO's managed voice channels, with sub-second transmissions and mobile audio that works with the screen locked. Your users keep their existing accounts.

your-app / voice.tsTypeScript
// Illustrative TypeScript integration
const ptt = new NeoClient({
  token: await yourApp.getVoiceToken(),
});
await ptt.connect();
await ptt.joinTalkgroup("logistics-bay-4");
 
talkButton.onPress(() => ptt.startTransmit());
talkButton.onRelease(() => ptt.stopTransmit());
ptt.onSpeakerChange(updateChannelView);
CHANNEL STATEReceiving

Logistics: Bay 4

Bay supervisor

Supervisor Override

Channel response
Sub-second

iOS PushToTalk integration

Android background services

Illustrative SDK usage and channel state. API details supplied with SDK access.

Applications

Workforce software

A store employee can call the stockroom from the app they use for shift tasks.

Fleet and dispatch

Drivers on in-cab tablets can speak with dispatchers working in a browser.

Security operations

A guard can call for assistance from an incident screen, with priority voice and recording.

Voice assistants

A worker presses to ask an assistant a question. The assistant can also join a team talkgroup.

Integration scope

Voice has to work through the whole shift.

Most of a radio's day is spent waiting for a call. For an app team, that means managing standby connections and mobile audio long after the user leaves the PTT screen.

Between calls

Workers need to hear the next transmission without keeping a full-duplex call open all day. NEO uses short transmissions and standby channels. Review battery use, reconnection and usage costs against your actual shift pattern.

When the phone locks

iOS suspension, Android Doze and headset buttons each affect audio behaviour. NEO's mobile SDK handles native background integration and the audio lifecycle, including calls received with the screen locked.

Inside your product

NEO has no prescribed user interface. Connect your identity provider, decide how talkgroups appear and keep voice within your own application. SDK licensing and deployment are part of the integration review.

Channel behaviour

How NEO handles a call

Short voice transmissions

QUIC / WebTransport carries voice, with fallback for restrictive networks. Transmission control and audio delivery are coordinated to preserve the first and last words of a call.

Who gets to speak

When two workers press PTT together, the server grants one the channel. Set role-based priority, queue requests on a busy channel and let a supervisor interrupt when needed.

Audio with the screen locked

Apple PushToTalk integration and Android background services keep voice available while another app is open or the screen is locked. Workers can receive calls without returning to the PTT screen.

A radio shared across shifts

The device stays at the site; the person using it changes. OAuth / OIDC token exchange ties the voice session to the worker signed into your application.

Changing network conditions

Adaptive encoding uses wideband voice on Wi-Fi and LTE, then reduces bandwidth use on congested cellular, rural and satellite links. We review the network requirements for your deployment with you.

Recordings and voice assistants

Optional hooks send talkgroup recordings to your cloud storage. Connect dispatch automation or a voice assistant to a live channel, with press-to-talk deciding when the microphone opens.

SDKs and hosting

Mobile and browser clients, connected to NEO

Pushytap NEO Flutter SDK

iOS and Android audio capture, acoustic profiles, background wake, lock-screen controls and hardware button events.

Pushytap NEO TypeScript SDK

Browser dispatch and command centres. Monitor multiple talkgroups and give authorised dispatchers hold-to-talk priority.

Pushytap NEO server

The server routes voice to talkgroups across thousands of endpoints and checks sessions against your identity provider.

  • Managed cloud or dedicated regional capacity
  • Talkgroup arbitration and priority
  • Audio routing, recording hooks and AI bridges

Your identity provider issues the user credentials. Your application exchanges them for a voice session; the NEO server enforces channel access.

PTT accessories

Keep the phone in a pocket.

NEO's mobile SDKs support external PTT buttons and audio on compatible accessories. Workers can press an accessory's talk button to transmit through your app and hear replies through its speaker or earpiece.

  • Bluetooth PTT speakerphones for voice and a physical talk button within reach.
  • PTT earpieces and headsets for listening and speaking through a worn accessory.
  • Remote speaker microphones (RSMs) clipped to a shoulder or lapel, with a speaker, microphone and PTT button.

Audio support and PTT button support depend on the accessory model and mobile operating system. Bring your device list to the integration review so we can confirm both.

Choosing an approach

What each integration asks of your team

WebRTC services such as LiveKit or Agora, PTT SDKs such as Zello, and a custom WebSocket implementation give you different starting points. Use these requirements to scope the work, including what your team will maintain after launch.

Pushytap NEO compared with general-purpose voice SDKs, legacy PTT apps and in-house development
CapabilityPushytap NEOWebRTC CPaaSLegacy PTT SDKIn-house WebSockets
Voice session modelHalf-duplex bursts with channel standbyUsually continuous, full-duplex sessionsVendor-managed PTT sessionsYou build transmission and session logic
Locked-screen audioNative mobile background integrationDepends on SDK and OS integrationDepends on vendor and mobile SDKRequires native OS lifecycle engineering
iOS PushToTalk / Android backgroundHandled by the mobile SDKEvaluate framework support and setupEvaluate vendor SDK supportYour team owns integration and maintenance
Standby economicsBurst-friendly deployment modelCheck participant-minute and connection feesCheck SDK licensing and seat costsInfrastructure plus engineering overhead
Application brandingHeadless; your UI, no vendor logosCustom UI; check licensing termsCheck branding and UI requirementsYour UI
Fringe-coverage voiceAdaptive, ultra-low-bandwidth modeEvaluate codec and reconnect behaviourEvaluate supported network conditionsYou build adaptation and recovery
IdentityYour OIDC / JWT identityTypically an application token serviceCheck user provisioning requirementsYou build authentication and session control

This table outlines integration responsibilities. It does not compare measured latency or prices. Check each provider's current SDK support and licensing against your requirements.

SDK access

Tell us what you're building.

Start with the app your workers use and the devices they carry. Our engineering team will work through the integration with you, from signing a user into voice to receiving calls during a shift.

What we'll discuss

  • Where Flutter, Kotlin or TypeScript fits your application
  • Devices, background audio and who can transmit
  • Hosting region and the number of connected devices

By submitting, you agree to be contacted about this enquiry.