Careful software, quietly made — for the home screens we'd want ourselves.
We design and build native mobile applications for iOS. Our focus is consumer software — the kind that earns its place on the home screen, and stays there.
From first sketch to shipped feature, we think carefully about how software feels in the hand. Information architecture, interaction, motion, and the thousand small decisions that separate a tool you tolerate from one you love.
Native iOS, built on Swift and SwiftUI. Lean stacks, clean architecture, shipped often. We write code we're happy to live with for years, because we usually have to.
Every product gets a name, a voice, and a visual system it deserves. Typography, colour, tone — the quiet details that make software feel like it was made by someone, not assembled.
“ Careful software,
made by a small team, for people who notice the details.
The best mobile apps are patient — they respect the person using them, they don't waste the battery or the attention of the people they serve, and they do one thing with unusual care.
We're a small studio by choice. The fewer hands a product passes through, the more of its character survives. Everything we make is designed, built, and maintained in-house.
Our work tends to live at the intersection of three things: thoughtful use of modern AI, everyday utility, and design you can feel. We're drawn to problems where those three meet.
Poole Technology is an independent app development studio based in the United Kingdom. We design and build mobile applications for consumers, working across product strategy, interface design, engineering, and brand. The studio is small by design: a handful of people, no agencies, no outsourcing. Every product passes through a single pair of hands from first sketch to App Store release.
We believe good software is a craft. It respects the person using it. It does one thing well. It doesn't waste the battery or the attention of the people it serves. The best apps on your phone are the ones you stopped noticing years ago — not because they're dull, but because they quietly do their job. That's the bar.
The best apps on your phone are the ones you stopped noticing years ago.
Our work tends to live at the intersection of three things: AI, everyday utility, and design you can feel. We think modern machine intelligence is still mostly being used to build novelty — demos that impress once, then fade. We're more interested in the quiet version: tools that understand what you're trying to do and remove a small amount of friction, every day, for years.
We ship our own products under our own brands, and occasionally collaborate with selected partners on theirs. We don't take on traditional agency work — no brochureware, no campaign microsites, no one-off contract jobs. What we make is meant to last.
Our work focuses on a handful of areas where we think modern mobile software can do meaningfully better than what's out there today. Specific titles are available on request.
Applications that use modern AI to help people capture, organise, and make sense of their day — without getting in the way. The test we apply: could a careful person do this themselves, given enough time? If yes, AI should save them that time quietly.
Apps that help people see, design, and decide. We care about colour, typography, and the small details that make creative software feel good to use. This is the area of our work most concerned with aesthetics.
Products that rethink the way people communicate on a device that is, still, fundamentally a phone. Voice is a neglected interface. We think there's room for software that treats speaking, listening, and being heard as first-class concerns.
All active consumer applications are available on the Apple App Store.
There is no universal method; every product is different. But the shape of how we approach a new piece of work tends to look roughly like this. Six stages, sometimes overlapping, rarely in a straight line.
Before we commit to a project, we spend time understanding what already exists. What's the user doing now? What tools do they reach for? Where do they give up? Most software is made without this step, which is why so much of it is redundant. Orientation is usually a week, sometimes two. It produces a written brief that the rest of the project answers.
We start on paper, not in Figma. Fast, rough, disposable drawings — sometimes dozens a day. The goal is to exhaust bad ideas cheaply and surface the one or two that aren't bad. Most of what we sketch is thrown away. That's the point.
The surviving ideas move into high-fidelity design. This is where the interface takes its final shape — typography, grid, colour, motion, micro-interaction. We prototype in tools the engineering team can read, because handing a static mockup to a developer is how small problems become large ones.
Native iOS, Swift, SwiftUI. We write our own code; we don't wire together third-party SDKs where we can avoid it. The first build is deliberately minimal — one screen, one feature, end-to-end — and then we grow it. No feature ships until it's been lived with for at least a week.
Most of our time is spent on the parts nobody sees: performance, accessibility, edge cases, the state of the app when your network drops, the state of the app after it hasn't been opened in six months. Shipping well means a product you can recommend to your mother without caveats.
A shipped app is not a finished app. We maintain what we build — OS updates, bug reports, the slow drift of App Store requirements. A product that isn't maintained is gradually broken by the world around it. We plan for this from day one.
A short list of the working principles the studio returns to. Not rules, exactly — more like a map of the assumptions underneath our decisions.
The industry's default frame is that software is a product — something engineered, measured, optimised. That's partly true. But the products that last are usually the ones whose makers treated them as craft: made with care, attention, and opinion.
Most apps fail by trying to do too much. The strongest products tend to start with a single, clearly-defined use — the kind of thing you can describe in a sentence — and resist every pressure to expand beyond it.
A consumer installs your app, and you appear on their home screen. That is the most valuable real estate in consumer software. Earning and keeping that place is the only real success metric.
The two scarcest resources on a phone. Every decision we make is costed against them. An app that drains either is a kind of quiet theft.
The separation between "design" and "code" is a convenience of bigger teams. In a small studio, the same person often does both, and the work is better for it. Typography is a performance decision. Motion is an architectural one.
The useful form of machine intelligence is the kind you stop noticing. Features that depend on the user marvelling at them are fragile; features that do their job quietly tend to last.
Most of the interesting work on a product happens after version 1.0. We aim for an honest first release and plan to live with it for years, not weeks.
Every additional person on a project dilutes its character. We believe in small teams not because we have to, but because we think the work is better that way.
Small decisions about language, measurement, and default settings carry a surprising amount of the feeling of a product. We think about them.
User data is not a resource. We collect the minimum, store it for the shortest time, and never use it as currency. This is easier than the industry pretends.
Short essays on the craft of making software, the shape of our practice, and the particular problems of building small products for a big platform. Written when we have something to say, not on a schedule.
The industry's default assumption is that studios grow. More people, more projects, more revenue. We've spent the last two years deliberately not doing this. A note on what it feels like to choose small, what we've given up, and what we think we've kept.
Most of the consumer-facing AI we see is still in its novelty phase — impressive demos, viral threads, products that fade within a quarter. We're interested in the other thing: the slow, boring, useful version.
The part of software nobody writes about, photographs, or gives talks about: keeping old things working. Every shipped app is a thing that must now be looked after, for as long as it lives on a phone.
For general enquiries, partnerships, press, or product support, get in touch by email. We read everything and reply to most things — usually within a few working days.
Poole Technology is an independent app development studio based in the United Kingdom. This privacy policy covers how we handle personal information in connection with our website, pooletechnology.co.uk. Each of our mobile applications has its own privacy policy, available on its App Store listing and within the app itself.
When you visit this website, we may collect basic analytics data such as pages viewed, approximate location at country level, device type, and referral source. This is held in aggregate and does not personally identify you. We also hold any information you provide voluntarily — for example, if you email us, we will have your email address and the contents of your message. We do not use advertising cookies and we do not sell data to third parties.
We use this information to understand how our website is being used and improve it, to respond to enquiries you send us, and to comply with our legal obligations. That is the full list.
Email correspondence is retained for as long as is reasonably necessary to address your enquiry and for sensible record-keeping. Aggregate analytics data is retained in line with our analytics provider's default retention period.
We use only strictly necessary cookies for basic site functionality. We do not use advertising, tracking, or cross-site cookies of any kind.
You have the right to request access to, correction of, or deletion of personal information we hold about you. You have the right to restrict or object to processing, and the right to data portability where applicable. To exercise any of these rights, email st113@pooletechnology.co.uk. You also have the right to lodge a complaint with the Information Commissioner's Office (ICO) at ico.org.uk.
We may update this policy occasionally. The "last updated" date at the top of the page reflects the most recent revision. Material changes will be announced on this page.
For any questions about this policy, please contact st113@pooletechnology.co.uk.