iOS support
A mobile Cocktel client with the same attention to audio behavior, accessibility, call state, and provider compatibility.
Roadmap
Cocktel is being designed beyond one Mac.
The macOS app is the first serious surface. The roadmap extends the same idea to mobile, Windows, managed deployments, and service-provider infrastructure without turning Cocktel into a generic PBX portal.
Roadmap
Planned directions
These items are not promised dates. They are the product directions Cocktel is being structured around, especially for organizations that need consistent behavior across users, devices, and networks.
Android support
A native Android client for teams and providers that need Cocktel outside the Apple ecosystem.
Windows support
A desktop client for organizations where Windows remains the main workstation platform.
Central provisioning
Managed account, profile, and policy configuration so deployments do not depend on manual setup per user.
Custom push servers
Provider-controlled push infrastructure for deployments that need tighter operational ownership.
Managed release channels
Predictable distribution paths for internal testing, beta groups, and production rollouts.
Useful conversations now
- Number of expected users and devices.
- Required platforms and timeline pressure.
- Whether provisioning must integrate with existing account systems.
- Push notification ownership, compliance, and hosting expectations.
- White-label or provider-specific requirements.
Contact
Discuss roadmap fit
If your deployment depends on one of these directions, send the constraints early. That is more useful than a generic feature request.