Owned and operated by A4T Studio

Pinglo: one lost-and-found product across iPhone and web.

Pinglo brings reports, sightings, claim checks, messages, safer returns, and private community feeds into one synced service. A4T Studio shaped the product, identity, delivery, launch, and continued operation.

Current Pinglo homepage showing the live lost-and-found feed on iPhone and a link to the web app
Live on iPhone and webOne account, synced across both
The problem

A familiar situation with no consistent process.

When an item is lost or found, information is spread across venues, social posts, messages, and informal handovers. People may not know where to report it, how to identify a genuine match, or how to arrange a safe return.

Pinglo was created to organise those steps across a phone or browser, while giving campuses, venues, and workplaces their own private feed.

A4T Studio's role

One project covering product, brand, launch, and operation.

Pinglo is an A4T Studio venture. The work therefore continued beyond a prototype or design file into the practical needs of a public service.

01

Product definition

Turned the broad problem into users, workflows, priorities, screens, trust requirements, and a focused first release.

Scope and product route
02

UX & interface

Designed reporting, discovery, sightings, claims, messaging, profiles, community feeds, and safety journeys around clear everyday actions.

Working interaction system
03

Product development

Managed the iPhone and browser builds, shared backend, live synchronisation, testing, release preparation, fixes, and product changes.

Live iOS and web product
04

Identity & public website

Created the visual identity, App Store presentation, product website, partnership route, support information, and trust pages.

Recognisable public presence
05

Launch

Prepared the App Store listing, product materials, policies, support routes, and release checks.

Public App Store release
06

Ongoing support

Continues to review the live product, plan improvements, support users, and manage future releases.

Active product operation
The live interface

A working product visitors can inspect.

These genuine product screens show the nearby feed, guided reporting, private claim checks, and messages. The same account now works through the browser app.

Pinglo nearby reports feed
01Nearby reports
Pinglo lost or found item reporting flow
02Guided reporting
Pinglo private detail claim check
03Private claim check
Pinglo private messages screen
04Private messages
Delivery route

Built as a sequence of decisions, not one large guess.

The process moved from defining the service to designing core journeys, building and testing the product, preparing launch, and supporting the live release.

01

Define

Clarify the users, problem, trust needs, and smallest useful product.

Product brief
02

Design

Map the key flows and turn them into an interface that can be built and tested.

UX and UI
03

Build & test

Develop the shared service across iPhone and web, review real behaviour, fix issues, and prepare public releases.

Release candidates
04

Launch & improve

Publish the product, support the service, and ship changes around live user and partner needs.

Monthly product releases
The result

A live service for individuals and busy places.

Pinglo is live on iPhone and in the browser. People can browse the feed, post reports, send sightings, verify claims, message privately, and join place-based communities with the same synced account.

Hotels, universities, stations, venues, gyms, and managed buildings can also use Pinglo as one front door for lost property, hand-in guidance, safety alerts, and safer returns.

A different idea?

Your app can solve a completely different problem.

Tell us about a customer need, work problem, repeated task, or new product idea. You do not need a technical brief for the first conversation.