Fail-closed routing
Self, absent, stale or unauthorized recipients are rejected without fallback to public talk.
CASE STUDY / 04
ONE Voice
PUSH-TO-TALK FOR FIELD TEAMS
IN USE · SKLAVOUNOS MEAT
This presentation uses the ONE identity. The documented functions are used at Sklavounos Meat. Portfolio naming does not change the architecture or installed applications.
An Android operational voice application for authorized staff, with channels, presence, explicit private talk and continued operation on the lock screen.
CURRENT STATESigned 1.8.3 candidate · no verified public Play release
00 / AT A GLANCE
The project at a glance.
PROBLEM
In the field, searching for a contact, unlocking the device and uncertainty about the correct channel add friction to immediate coordination.SOLUTION
Android push-to-talk with controlled enrollment, role- and location-scoped channels, presence, explicit private talk and lock-screen continuity.IN USE BY
Approved staff and approved devices, with no public user registration.OPERATES ACROSS
Android, using a foreground service for background and lock-screen operation, together with controller gestures.MY ROLE
Product design and UX, Android, realtime/backend integration and Play release engineering.STATUS
Signed 1.8.3 candidate, versionCode 22; no public Google Play release has been verified. The documented Play distribution remains Internal testing for the earlier 1.0.0 release.01 / THE NEED
The team needs to talk without stopping the work.
In a field environment, searching for a contact, unlocking a phone and uncertainty about the right channel add friction at the exact moment immediate coordination is required.
- Each user should see only the channels and recipients permitted by their role.
- Public channel talk and private talk must be two explicit, non-confusable actions.
- Audio should continue with a clear foreground notice when the app moves to the background or the screen locks.
02 / IN PRACTICE
Immediate voice with explicit permissions.
ONE Voice combines immediate voice communication with explicit permissions and fail-closed behavior.
- Each user sees only the location-scoped channels, recipients and presence permitted by their role.
- Public and private talk remain explicitly separate; an invalid or unauthorized private recipient is rejected without fallback to a public channel.
- Audio continues in the background and on the lock screen with a clear foreground notice, while short and long controller gestures support use during the workday.
03 / ONE VOICE
Three moments in the same conversation.
Illustrative presentation screens using the ONE identity, with synthetic roles and channels only. These are not production captures.
Illustrative ONE interface in English with synthetic data — not a production capture or evidence of real conversations.
04 / THE SOLUTION
Fast voice with strict boundaries.
Speed does not come from weaker safety. Device, user, channel and recipient are verified before each permitted workflow.
- 01
ENROLLMENT
Approved device
Activation is controlled by an administrator and credentials are protected with Android Keystore. - 02
PRESENCE
Channels and availability
The user sees location-scoped channels and the permitted presence of the team. - 03
TALK MODE
Public or private talk
Private talk requires an explicitly selected recipient and never silently degrades into a public channel. - 04
FIELD USE
Background and controller
Foreground service, lock-screen continuity and short/long controller gestures for use within the workday.
ONE Voice is an application for a closed operational audience, not a public social network or emergency service.
05 / SAFETY BY DESIGN
Failure never changes the recipient.
Critical decisions fail closed. A missing, stale or unauthorized private recipient never triggers an automatic public transmission.
Backend authorization
Role, device, channel and recipient grant are rechecked by the backend rather than trusting the client UI.
Two voice models
Live audio is ephemeral, while directed store-and-forward bursts of up to 30 seconds remain encrypted only until their defined purge.
Signed candidate
The 1.8.3 candidate includes signed APK/AAB artifacts, unit tests, Android lint and signature verification.
06 / SCALE & EVIDENCE
A specific candidate with explicit boundaries.
These figures describe the signed candidate and documented release engineering. They are not measures of production usage.
- Version / versionCode
- 1.8.3 / 22Signed APK and AAB candidate; not verified as a public Play release.
- Android SDK range
- 26 → 36Minimum SDK 26 and target SDK 36 in the verified candidate.
- Directed burst
- ≤ 30sThe store-and-forward model supports directed bursts of up to thirty seconds.
- Focused backend tests
- 30 / 30The focused backend suite passed during 1.8.3 preparation.
SIGNED CANDIDATE / PLAY TRACK30 August 2026 / 4 August 2026
07 / TODAY
Signed candidate, without public Play confirmation.
Version 1.8.3 (versionCode 22) is complete and signed as a candidate, but there is no evidence that it has been uploaded to or approved by Google Play. The only verified Play distribution is the earlier 1.0.0 release in Internal testing for two approved accounts. This page therefore shows no public install badge or public Play link.
NEXT GATE
- 01Complete the required Play review / production process.
- 02Verify acceptance on two physical devices.
- 03Complete the final privacy and Data Safety review.
- 04Show the exact public version and availability state.
08 / CONTACT
Does an operational workflow need a clearer system?
Describe the current process, the tools you use and the point where time, information or control is being lost. The first conversation clarifies the need and the boundaries of a solution.