Workforce software
A store employee can call the stockroom from the app they use for shift tasks.
Pushytap NEO · Embedded push-to-talk infrastructure
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.
// 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);Bay supervisor
Supervisor Override
iOS PushToTalk integration
Android background services
Applications
A store employee can call the stockroom from the app they use for shift tasks.
Drivers on in-cab tablets can speak with dispatchers working in a browser.
A guard can call for assistance from an incident screen, with priority voice and recording.
A worker presses to ask an assistant a question. The assistant can also join a team talkgroup.
Integration scope
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.
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.
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.
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
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.
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.
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.
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.
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.
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
iOS and Android audio capture, acoustic profiles, background wake, lock-screen controls and hardware button events.
Browser dispatch and command centres. Monitor multiple talkgroups and give authorised dispatchers hold-to-talk priority.
The server routes voice to talkgroups across thousands of endpoints and checks sessions against your identity provider.
Your identity provider issues the user credentials. Your application exchanges them for a voice session; the NEO server enforces channel access.
PTT accessories
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.
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
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.
| Capability | Pushytap NEO | WebRTC CPaaS | Legacy PTT SDK | In-house WebSockets |
|---|---|---|---|---|
| Voice session model | Half-duplex bursts with channel standby | Usually continuous, full-duplex sessions | Vendor-managed PTT sessions | You build transmission and session logic |
| Locked-screen audio | Native mobile background integration | Depends on SDK and OS integration | Depends on vendor and mobile SDK | Requires native OS lifecycle engineering |
| iOS PushToTalk / Android background | Handled by the mobile SDK | Evaluate framework support and setup | Evaluate vendor SDK support | Your team owns integration and maintenance |
| Standby economics | Burst-friendly deployment model | Check participant-minute and connection fees | Check SDK licensing and seat costs | Infrastructure plus engineering overhead |
| Application branding | Headless; your UI, no vendor logos | Custom UI; check licensing terms | Check branding and UI requirements | Your UI |
| Fringe-coverage voice | Adaptive, ultra-low-bandwidth mode | Evaluate codec and reconnect behaviour | Evaluate supported network conditions | You build adaptation and recovery |
| Identity | Your OIDC / JWT identity | Typically an application token service | Check user provisioning requirements | You 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
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.