Trinity Logic Ltd – Faces in Places

Some projects are ahead of their time. Faces in Places was one of them.

Long before Facebook normalised the idea of being tagged in a photo from a night out, before Instagram existed, and before smartphones made everyone a photographer, Trinity Logic built a platform that connected professional venue photographers with the people in their pictures — and created a commercial model around it. The site was facesinplaces.co.uk, and it operated at a moment when the concept of finding and owning a digital photo of yourself from a night out was genuinely novel.

The core idea was straightforward: pubs, bars, restaurants, and nightclubs across the UK signed up to the service. Their photographers captured images throughout the evening. Those images were uploaded to the platform, tagged by venue and date, and made available for the people in them to find, view, and purchase — billed directly through their mobile phone using the premium SMS infrastructure we had already built through the mobile content platform.

What We Built

Venue network and photographer workflow — the supply side of the platform was a network of signed-up venues across the UK, each with photographers producing content on a regular basis. The platform included tools for photographers and venue managers to upload image batches, organise them by event and date, and publish them to the public-facing site. Managing the quality, volume, and metadata consistency across dozens of venues required a robust back-end content pipeline.

Photo discovery — users arriving at the site could browse by venue, by date, or by event. The search and discovery layer was designed to make it easy to find yourself in a photo from a specific night at a specific place — which, in the absence of facial recognition technology, meant getting the venue and event taxonomy right and making the browsing experience fast enough to hold attention.

Mobile premium billing for purchases — photo purchases were completed through the same premium SMS shortcode infrastructure as the mobile content platform. A user who found their photo would enter their mobile number, receive a confirmation text, reply to authorise the charge, and receive a link to download the full-resolution image — billed to their phone contract. This was the right model for the era: most people had a mobile with a contract but relatively few had credit cards they were comfortable using online, and mobile billing removed that friction entirely.

User accounts and social features — registered users could save favourite photos, share links, and — in what would now be recognised as an early form of social tagging — notify friends that there were photos from a particular event. The social graph was primitive by later standards, but the intent was there: people finding and sharing photos of themselves and their friends in the places they’d been.

A Platform Before Its Time

Facebook launched in 2004 and began its UK expansion around 2006–2007. Myspace was gaining traction. Camera phones were becoming common but were still low resolution. The idea of a platform built around social photos from real-world venues — connecting people to images of themselves and their friends, monetised through digital purchasing — was not yet a mainstream concept.

Faces in Places was doing exactly that. The venue-based photo discovery model, the social sharing mechanics, the idea that an evening out could generate digital content that people would want to find and own — these were the right instincts at the right time. With the network effects and capital that would later fuel Facebook, Instagram, or any of the nightlife photography apps that emerged in the 2010s, the model had legs.

What it lacked was scale and timing. Building a two-sided marketplace — venues on one side, consumers on the other — requires critical mass on both sides simultaneously, and doing that as a bootstrapped operation in the mid-2000s, before social sharing was a reflexive behaviour, was a significant challenge. The platform was commercially active and the model worked, but growing the venue network fast enough to generate the consumer traffic that would justify further investment proved difficult in the pre-smartphone, pre-social-media landscape.

Technology

The same open source philosophy that guided the smart metering and mobile content platforms applied here. Java on Linux, Apache Struts, Apache Tomcat, and MySQL — a stack that could be operated at low cost, understood completely, and scaled on commodity hardware. The premium SMS billing layer reused and extended the O2 SOAP integration built for the mobile content platform, demonstrating the value of designing integrations as reusable components rather than point solutions.

Image handling at scale was a genuine technical challenge for the era — storing, resizing, and serving photo assets efficiently without the cloud storage and CDN infrastructure that is now taken for granted required careful design of the local storage and serving layer.

Outcome

Faces in Places ran as a live commercial service, processed real transactions, and built a genuine venue network across the UK. It was a working proof of concept for a model that the wider industry would validate comprehensively over the following decade. The timing, the bootstrapped capital constraints, and the absence of the social infrastructure that would later make photo sharing frictionless meant it didn’t reach the scale it might have with different conditions.

It remains one of the projects I look back on with the clearest sense of what might have been — and with genuine satisfaction that the engineering and the business model instincts were sound.

Apache Tomcat MySQL O2 UK