Trinity Logic Ltd – Mobile Content Platform

Before the App Store, before smartphones, before streaming — there was the Nokia era. And in that era, premium mobile content was a genuine commercial opportunity. Ringtones, wallpapers, and MMS graphics were things people actively paid for, delivered directly to their handsets via SMS shortcodes and billed through their mobile contract. Trinity Logic Ltd built a platform to operate in exactly that space.

This was one of several SaaS products developed through Trinity Logic in the early-to-mid 2000s, at a time when the UK mobile content market was growing rapidly and the infrastructure to serve it was still being invented. The opportunity lay in building reliable, scalable delivery pipelines on affordable open source technology — keeping margins healthy in a market where operator integration costs could otherwise be prohibitive.

What We Built

The platform was a WAP-based mobile content store — built to the WML and XHTML-MP standards that Nokia and other handsets of the period required — where users could browse, select, and purchase ringtones and graphics. Purchase triggered an MMS delivery to the handset and a billing event routed through the operator’s premium shortcode service.

Premium SMS shortcode integration was the commercial backbone. Users would either browse and purchase directly through the WAP site, or respond to shortcode campaigns — texting a keyword to a premium number to trigger content delivery and billing. Trinity Logic held a commercial arrangement with O2 to operate through their shortcode infrastructure, giving us access to their subscriber base and their billing rails.

SOAP integration with O2 was the technical centrepiece of the billing and delivery flow. When a purchase was initiated — whether through the WAP site or via an inbound SMS — the platform made a SOAP call to O2’s premium service API to authenticate the subscriber, initiate the billing transaction, and confirm delivery authorisation before the content was dispatched. Error handling, retry logic, and transaction reconciliation all had to be built explicitly: SOAP-era integrations offered none of the observability tooling available today.

MMS delivery handled the actual content dispatch — constructing well-formed MMS messages containing the ringtone or graphic and routing them through the operator’s MMSC. At the time, MMS interoperability between operators and handset models was inconsistent, which meant building a content adaptation layer to handle the variation in what different Nokia models could receive and render correctly.

Content management and catalogue — the back-end included tooling for managing the content library: uploading ringtones (polyphonic, then later true-tone MP3s as handsets evolved), resizing and formatting graphics for different screen dimensions, and organising the catalogue into browsable categories.

Technology

The entire platform was built on open source infrastructure — a deliberate strategic choice to keep operational costs low and avoid vendor lock-in in a market where margins depended on it. Java on Linux, Apache Struts for the MVC layer, Apache Tomcat as the application server, and MySQL for persistence. The SOAP integration with O2 was built using Java’s early XML and web service libraries — verbose by modern standards, but effective.

Running on Linux rather than Windows Server was an early commitment to the open source philosophy that has remained consistent throughout my career: proprietary infrastructure costs compound at scale, and the transparency and community support of open source stacks more than compensate for the absence of vendor support contracts.

Outcome

The platform operated commercially, processing real transactions and delivering content to subscribers on the O2 network. It was a functioning end-to-end business: content, delivery, billing, and reconciliation all running on infrastructure Trinity Logic owned and operated.

The mobile content market ultimately consolidated rapidly as handset capabilities and consumer expectations shifted. The arrival of the iPhone in 2007 and the subsequent app economy made the WAP-era content model obsolete within a few years. But the commercial and technical experience of building and operating a live billing integration with a major UK mobile operator — handling real money, real subscribers, and real delivery SLAs — was formative. The discipline of building operator-grade reliability on commodity open source infrastructure has informed how I approach every integration project since.

O2 UK Apache Tomcat MySQL