What problem does it solve?
Field teams need operational communications that remain connected to work context, roles and rugged/mobile devices.
Part of HalNora One · Independent product
Published / field validationOperational communications
Messaging and push-to-talk built around operational work.
HalNora Communications is being developed for dispatchers, drivers, workers and operational teams where presence, background behaviour, device controls and network resilience matter as much as the conversation itself.
Designed around
- Dispatch and Driver integration
- Delivery and transportation
- Field-service teams
- Hospitality and events
- Security/operational crews
- Rugged-device deployments
Current status
The standalone Communications app is published and has a successful native build. V22 browser/PWA Dispatch↔Driver two-way audio has been observed, but intermittent same-Wi-Fi peer loss prevents the current PTT field gate from passing. The V22 ptt_field_qa gate remains Pending and no production-release claim is made.
Product vs integration evidence
Standalone Communications has stronger field evidence; V22 direct-radio acceptance remains separate.
The standalone Communications app is published. Browser↔Android direct PTT has been observed with one audio peer and zero packet loss, and Samsung Note 10+ / M53 Bluetooth produced clear two-way and locked-screen audio. Automatic Bluetooth route re-application after reconnect, Motorola/permission-denial coverage and full network-loss recovery remain open. V22 Dispatch↔Driver acceptance is a separate optional integration gate.
Live development statusPublished / field validation
Current focusStabilize the V22 Dispatch↔Driver direct-radio connection, then finish network-handoff/native-package/locked-screen acceptance within the approved scope; Bluetooth and broader rugged-device work remain separate.
Last updatedOctober 20, 2026
The live status feed is temporarily unavailable. Showing the last published snapshot.
Investor view
Problem, capability, connection and current stage.
HalNora separates demonstrated development progress from future product direction so scope can be understood without treating roadmap items as commitments.
What is it being built to do?
Operational messaging, presence and native push-to-talk designed for dispatchers, drivers, technicians and field teams.
How does it connect?
Can serve Dispatch, Field Service, Hospitality/Event Operations and other HalNora products while retaining its own communications authority.
Where is it today?
The standalone Communications app is published and has a successful native build. V22 browser/PWA Dispatch↔Driver two-way audio has been observed, but intermittent same-Wi-Fi peer loss prevents the current PTT field gate from passing. The V22 ptt_field_qa gate remains Pending and no production-release claim is made.
Current direction
What this product is being built to do.
Public descriptions reflect current development direction and do not imply general availability or production certification.
Direct messaging
Support dispatcher-to-worker and person-to-person communication with delivery/read state and history.
Work-linked conversations
Associate communication with the job, task or operational context that caused it.
Push-to-talk
Provide low-friction voice communication for individuals and teams using mobile and rugged devices.
Background & lock-state behaviour
Use native Android capabilities so operational PTT can remain useful while devices are locked or another app is foregrounded.
Network reconnect resilience
Recover across Wi-Fi and cellular changes or temporary connectivity loss.
Rugged-device controls
Map supported physical PTT buttons and expose capability diagnostics for deployment-specific hardware.
Presence & channels
Use role- and permission-aware channels, worker presence and work context instead of open consumer-chat patterns.
Notification preferences
Support meaningful notification preferences while avoiding noisy telemetry as user-facing alerts.
Secure attachments roadmap
Add permission-scoped attachments and richer work-linked communication without weakening privacy or auditability.
Driver integration
Reuse the native PTT transport inside Driver while Dispatch/Driver continue to own identity, work context, permissions and UI.
Product boundary
Communications owns communication transport and history.
Communications owns messaging/PTT transport, conversation history and communications state. Operational products supply authorized work context and permissions. HalNora does not assume every PTT conversation or camera feed should be recorded.
HALNORA ONE ARCHITECTURE
Connected, not coupled.
Cross-product workflows use explicit contracts, authenticated events and clear authority so one product does not silently take over another product’s records.
How the HalNora platform works →Recent native validation
Standalone PTT has credible field evidence while broader device acceptance continues.
Current standalone testing has moved beyond earlier crash and reconnect failures. Broader device and hardware-key coverage still remains before production certification.
Two-way PTT
Two-phone PTT is working reliably in the current native test build without the earlier connection crashes.
Locked-screen receive
Receive behaviour has passed with phones locked, and lock/unlock cycles no longer require users to rejoin the channel.
Network recovery
Wi-Fi → cellular and cellular → Wi-Fi transitions have passed current field testing.
Physical-key mapping
Foreground physical PTT-key mapping has been demonstrated. Locked-screen hardware-key initiation and broader rugged-device coverage remain validation work.
What comes next
Development priorities.
HalNora prioritizes reliability, security, recoverability and real-world validation over feature count alone.
Search themes: push-to-talk app, PTT for field teams, dispatch communications, rugged device PTT, driver communication software, operational messaging.
Product inquiry
Interested in Communications?
Talk with HalNora about product direction, commercial use cases, partnerships or investment.