bonbon is Hrvatski Telekom's flexible, no-contract mobile brand. Moberg contributed to the development of its Flutter mobile app as part of the wider telco delivery organisation — and maintains it now that it's in every pocket it needs to be in.
bonbon is Hrvatski Telekom's prepaid, no-contract mobile brand in Croatia — part of the Deutsche Telekom group. Launched in 2010, bonbon built its identity on flexibility: instead of fixed tariffs, users compose their own mix of voice, SMS and data. For a brand like that, the mobile app is not an accessory — it is the shop, the account desk and the tariff configurator in one.
Moberg worked on the development of the bonbon mobile app as a development partner within Hrvatski Telekom's wider delivery organisation — one contributor in a larger, structured telco setup, not the sole author. The app is in production, and the engagement has moved into maintenance: keeping a national brand's primary customer channel healthy, release after release.
The app is built in Flutter — one codebase compiling to both iOS and Android. For a prepaid brand whose users span every kind of device, that decision does real work: features ship to both platforms simultaneously, behave identically, and cost one team's effort instead of two. Parity between platforms stops being a coordination problem and becomes a property of the architecture.
The less visible half of the solution is organisational. A Deutsche Telekom-group company does not run projects casually: there are defined processes, review gates, security requirements and release procedures, and every partner in the delivery chain is expected to operate inside them. Moberg's contribution was engineered to that bar — code, documentation and delivery practices that hold up in an environment where they are checked, not taken on faith.
With the app live, the work is maintenance in the honest sense: OS updates, framework upgrades, evolving requirements from the brand, and the steady grind of keeping a production app current on two platforms from one codebase.
Working inside a large telco delivery setup means aligning with other teams, other vendors and established processes. The skill is contributing at full quality without owning the whole board.
A global telco group sets explicit expectations for security, process and delivery quality. Meeting them is the entry ticket, not the achievement — and it shapes how every line of code is written and shipped.
For a no-contract, self-service brand, the app carries the customer relationship. Instability there is not a technical incident — it is a brand problem, visible at national scale.
bonbon's users get one app that behaves the same whichever platform they hold, and the brand gets features that land on iOS and Android at the same time — the practical dividend of the Flutter decision. For a prepaid brand whose entire proposition is self-service flexibility, an app that simply works is the product promise kept.
For Hrvatski Telekom, the value is a development partner that fits its machine: Moberg delivers inside the group's processes and standards rather than around them, and stays accountable through the maintenance phase. Passing a global telco's bar for its partners is not something a company can claim — only something it can keep doing.
One codebase, two platforms — simultaneous releases and identical behaviour on iOS and Android.