Tom Murton Makes things

London ShippedCutRoof 1.4, 17 Nov 2026 WroteBuilding the photography app I wanted while travelling, 19 Jul 2026

Project story / LightScout · 19 Jul 2026

Building the photography app I wanted while travelling

LightScout was my first app and it is still the project I care about most. It sits directly between two things I love: travel and photography. The original frustration was familiar from almost every trip. I could arrive somewhere remarkable and still spend too much time cross-referencing maps, weather, sunset times and other people's photo guides before I knew where to go.

I wanted the app I would open in that moment. Tell it where I am, what camera I have and how experienced I am; get a useful guide to where to stand, when the light is likely to work and what might be worth photographing.

The first version aimed too narrowly

I initially thought about LightScout as a tool for serious photographers. That pushed the product towards technical depth: camera settings, weather detail, landscape features, sun information and increasingly elaborate analysis. Those things can be valuable, but the framing assumed the user already knew what kind of answer to ask for.

The stronger need was much more ordinary. Most people travelling with an iPhone or camera are not trying to plan a professional shoot. They want to know what is worth seeing, where the interesting angle is and whether there is a better option than the same crowded viewpoint everyone else found on Instagram.

That led to a broader and clearer product. Near Me can analyse the area around the user. Hidden Gems looks for less obvious locations. Other modes focus on views and nature, city scenes or architecture. The recommendations still adapt to equipment and experience, but the interface no longer expects someone to think like a professional before the app can help.

The pivot was not from advanced photography to basic photography. It was from describing the technology to solving the moment.

Building without writing the code myself

I have already written the detailed story of how the first version reached the App Store: roughly 100 hours over six months, an early vibe-coded prototype, a complete rebuild and a workflow where AI tools produced the Swift while I supplied the requirements, product decisions and review process.

The headline is that AI tools generated a native iOS app. The real lesson was that the quality of the product work still determined whether the code went anywhere useful. The first prototype appeared quickly and became difficult to maintain. Clear phases, written specifications and reviews from multiple models made the rebuilt version shippable.

The App Store added a different kind of education. Subscriptions, authentication, privacy material, screenshots, provisioning and review all had to work as a system. LightScout was rejected twice before approval, both times for fixable issues. Getting to the point where Apple could review it was harder than the individual corrections.

The product keeps moving

Shipping did not freeze the original idea. LightScout now combines location scouting, weather, light, mapping and AI-generated guidance in a native iPhone app. The marketing site has also grown into a library of free destination guides, which serves the same underlying job even before someone downloads anything.

The shift towards travellers has made prioritisation easier. A feature earns its place if it helps someone decide where to go, when to go or what to try when they arrive. Technical sophistication is useful only when it improves one of those decisions. More data is not automatically a better scout report.

Why it remains my best project

LightScout is not my best project because it has the largest audience or because every part is finished. It is the best expression of how I like to work. It began with a problem I understood personally, forced me to learn an unfamiliar delivery process and kept changing as the product became clearer.

It also changed my relationship with AI development. Before LightScout, I could discuss the tools and their likely impact. Afterwards, I had dealt with the architecture, migrations, reviews, broken integrations and store constraints that sit between a convincing demo and a real product. That practical understanding has carried into everything I have built since.

The app is still the same promise I wanted on my own travels: spend less time researching the photograph and more time being in the place where it might happen.

Visit LightScout ↗ · Read the original build story ↗ · View on the App Store ↗

← All writing

Products, tools, experiments and the thinking behind them

What I’m working on, still in motion.

I help teams make better product decisions, then build things myself to keep those instincts honest.

Shipped CutRoof 1.4, 17 Nov 2026
Wrote Building the photography app I wanted while travelling, 19 Jul 2026

Made with AI agents. Claude Code, Codex and Gemini write the code. I decide what gets built and review what comes back.

Field notes

Sometimes I write about the decision before I know whether it was right.

  1. Building the photography app I wanted while travellingLightScout began as a tool for serious photographers. Its better direction was simpler: help anyone arrive somewhere new and find a genuinely good place to take a photograph.
  2. From a morning-routine Google Doc to Rest+RiseHow a personal routine tracker became a science-backed mobile app — and what shipping it on iOS and Android taught me about cross-platform development.
  3. Can an AI model research, build and ship a fun iPhone game?Why I built a benchmark around the whole product journey — not another isolated coding task — and what the first runs are revealing.
  4. What it took to turn Warden from a brainstorm into a gameThe design work, simulation and repeated rule changes behind a deterministic tactics game that finally became genuinely fun.
  5. Building the day-trip planner I actually wanted to useSomewhere began as a Replit hackathon project, but the problem survived the event: finding a genuinely good day out without doing an evening of research first.
  6. Trying to make AI app videos without the AI slopAn experiment in using generative video to explain the apps I build without producing the glossy, generic content people have learnt to ignore.
  7. The Case for Becoming a More Product-Focused Engineering Leader ↗
  8. Bridging the Gap: How Engineering Leaders Can Foster Better Collaboration with Product ↗
  9. In Defence of Estimates ↗
  10. Frictionless Internal Movement ↗

On stage

Talks about teams, systems and making better work possible.

  1. Frictionless Movement ↗LeadDev London. Companies often make it easier to resign than to change teams. This talk makes the case for frictionless internal movement and shows how a Transfer Window can work in practice.

About

A product lead with an engineering background, and a persistent need to make things.

I have spent my career helping teams make better product decisions. Building native apps, games and small experiments gives me a direct view of what happens after the roadmap — when the idea meets the code, the store and a real user.

Made with AI agents. Claude Code, Codex and Gemini write the code. I decide what gets built and review what comes back.

Read the CV · LinkedIn · Build notes on X · GitHub