A cross-platform softphone built by a Bulgarian team. It only does the client, which keeps it neutral towards every SIP provider.
# Desktop sits at 5.x, mobile at 2.x, and the two lines have run in parallel for years. That untidy rhythm is normal for client software.
Look at Zoiper's version numbers and they seem messy: desktop at 5.x, Android stable at 2.26, beta at 2.27, iOS on yet another sequence. This is not mismanagement; it is the normal state of a client product.
Desktop and mobile have completely different stacks, distribution channels and review cycles. Desktop can ship a point release whenever; mobile waits for store review and then deals with vendor-specific system restrictions. Forcing one version number only complicates the release process.
The practical approach is independent evolution per platform under one product name. Users see Zoiper 5; engineers see four release pipelines.
Mobile betas concentrate on three things: call stability, especially during network handover; audio routing, meaning the logic of switching between Bluetooth and speaker; and interface refactoring. Individually unremarkable, together they decide whether the app feels smooth.
Eighty percent of softphone iteration is fixing 'it should have rung and it did not'.
Production environments — agents, front desks — should stay on stable builds and wait one point release before upgrading, letting others find the problems first. Betas suit technical users willing to report issues, not critical desks.
Export the account configuration before upgrading. Softphone settings are numerous — server, transport, codecs, ringtones — and re-entering them is slow.
Release frequency across communications clients is generally slowing while each release carries more weight. Basic calling stabilised long ago; what changes now is edge cases and system compatibility. For users that is a good signal: the product has moved past the feature-accumulation stage.