One Codebase, Nine Platforms: How Siperb Ships a Softphone Without a Platform Team

LONDON - June 9, 2026 - PRLog -- By Justin Downes, Independent Technology Writer covering enterprise communications and AI

Justin Downes spoke with Conrad De Wet of Siperb about a design choice that has shaped the company's whole product strategy: shipping a single softphone codebase across roughly nine platforms — mobile, desktop and every major browser — with no dedicated team for any one of them.

It sounds reckless until you see what it saves.

In his OpenSIPS Summit talk in Bucharest, De Wet explained that Siperb set out to build one user experience: one interface, one core codebase, rendering everywhere. For most softphone vendors the alternative is the company itself — separate iOS, Android, desktop and web teams, with the roadmap set by whichever ships slowest.

His view is that this is no longer a forced choice. The web stack — React, JavaScript, WebRTC — is now expressive enough that a softphone's UI needs no native code, only a thin platform layer beneath it to handle what only the OS can do.

The layered architecture

Siperb's mobile client is built in layers: a hardware layer for calling at the OS level, a UI layer rendering the app, and a branding layer on top for customisation. The UI is a web view, with React Native as the container and the JavaScript engine doing the work. De Wet was candid about the trade-offs: mobile operating systems unload the app aggressively, so his team built workarounds. But this is not a game or a 3D engine — it is buttons and clicks, which render well on a phone.

The payoff, in his words, is fantastic. A feature shipped on Tuesday morning reaches every platform by Tuesday afternoon. There is no waiting for the Android team to catch up to iOS — there is no Android team.

The trade-offs

The honest version includes what does not work out of the box. Mobile push notifications behaved badly enough that Siperb had to build a custom service to solve them. Background behaviour still needs care. But these are bounded problems, not the permanent overhead of running three platform teams.

What to watch

Single codebase, layered architecture, web-rendered UI everywhere — this is becoming the default for new entrants in real-time communications. The question for 2026 is what happens to incumbents whose whole organisation assumes each platform needs its own team. Those who solved cross-platform a decade ago by hiring native developers in parallel will struggle hardest to compete on velocity.

Siperb's cross-platform softphone is at siperb.com.