In 2007, the first iPhone shipped without a panoramic camera. We saw the gap, built the solution, and sold it to 30,000 people in 52 countries before Apple made it redundant. This is the story of designing an app people loved — from a blank screen to the App Store in record time.
When Apple released the first iPhone in 2007, it arrived to enormous excitement — and a noticeable absence. There was no built-in way to capture the wide, sweeping images the device's camera was physically capable of. A colleague with deep expertise in JPEG compression algorithms saw the gap before almost anyone else did.
iPhone users wanted a simple way to stitch multiple images into panoramas. Existing solutions were limited or clunky — none were designed from the ground up for the iPhone's touch interface and physical constraints.
The App Store was brand new. Early movers had a genuine advantage — visibility was earned by showing up first with something people actually needed, before the category became crowded.
Create an app intuitive enough to require no instructions, fast enough to feel effortless, and language-agnostic enough to sell globally — all on the most constrained computing device most people had ever owned.
The development cycle was compressed by necessity and energised by opportunity. Five major versions over two years, each one shaped by real user behaviour rather than assumed preferences.
The core interaction mechanic came early and proved to be the right call from day one. Rather than asking users to take photos and then select them for stitching, the app guided the shooting sequence in real time. The right edge of one photo overlapped with the left edge of the next — giving users a live alignment guide built directly into the shooting experience. No instruction needed. No learning curve.
Actions — Stitch, Cancel, and Remove — were communicated entirely through iconography. No text labels. This was a deliberate global-market decision: an app that worked identically in Tokyo, São Paulo, and Auckland was an app that could sell in all three.
Version 1 went live faster than anticipated — catching the team off guard but delivering something more valuable than a perfect launch: early adopter enthusiasm. Word spread through photography forums and technology blogs. Media reviews drove sales spikes that could be traced directly to specific coverage. The feedback loop between real users and the next iteration began immediately.
A simple promotional website was built overnight to support the launch — evidence that in the early App Store era, presence and clarity mattered more than polish.
Version 2 added bidirectional stitching — users could now build panoramas from left to right or right to left, removing the one significant constraint the initial design carried. Email sharing followed, responding to the most consistent user request and completing the loop from capture to share. Each of the five releases addressed something real, observed in how people were actually using the app.
The discipline applied to feature decisions was as important as the decisions themselves. A principle emerged from the process: do nothing unless there is overwhelming demand. Most feature requests were declined. Simplicity was treated as a design value to be actively defended, not a starting point to be grown out of.
A turning point came after attending usability and marketing conferences and applying a single insight to the App Store listing and promotional copy: people do not buy features, they buy outcomes. Rewriting the product description around what users would experience — the feeling of capturing a scene the way your eyes actually see it — rather than how the stitching algorithm worked, produced a measurable 20% increase in sales over four months. Same product. Different story.
The design choices that defined Panorama were not all made upfront. Some were discovered under pressure, some arrived from unexpected directions. All of them held.
Rather than a tutorial or help screen, the alignment guidance was baked directly into the shooting interface. The visual overlap between the previous and current frame told users exactly what to do — without a single word of instruction. The constraint of designing for a global market drove a better interaction pattern than a purely domestic brief would have produced.
The most frequent pressure on the product was to add features. The most important decision made repeatedly was to refuse. "Do nothing unless there's overwhelming demand" was applied as a filter to every request. The result was an app that remained coherent and fast across five releases — one that never became cluttered by features added to satisfy individual users rather than serve the majority.
Designing the interface around icons rather than text labels was an upfront decision with compound returns. The app required no localisation, could be reviewed and recommended in any language, and never created the friction of a translated interface that reads awkwardly. A single binary shipped to 52 countries without modification.
The shift from feature-led to benefit-led marketing copy was the highest-return change made across the entire two-year run. Users do not care how the stitching algorithm works. They care that they can capture the view from the top of the gondola the way it actually looked. Reframing the product description around that experience produced a 20% sales increase in four months.
For a two-person operation built on a developer's compression expertise and a designer's conviction that simplicity was the product, the market response was validation of the approach as much as the artefact.
The product ran for two years before market competition and Apple's own hardware and software evolution made ongoing maintenance unsustainable. When iOS 6 introduced native panoramic photography in 2012, it was the best possible signal that the original opportunity had been real — and had been well served.
The 20% sales increase from rewriting product copy was not a marketing experiment — it was a design correction. How a product is described shapes how it is understood, and how it is understood determines whether someone downloads it. Messaging belongs in the design process from the start, not after the product is built.
The pressure to add features was constant. Most of it came from genuine user feedback. The discipline was in distinguishing between what a vocal minority wanted and what the majority needed — and recognising that the majority was well served by the product as it was. Saying no to reasonable requests is one of the hardest and most important design skills.
The App Store in 2007 was a level playing field that would never exist again. Moving fast and shipping something real — even imperfect — earned traction that no amount of later investment could replicate. The word-of-mouth that drove early sales came from people who discovered something genuinely useful before the category was crowded. That window was finite, and the product was in it.
The choice to use icons instead of text was made early, for practical reasons — and produced compounding returns. A language-agnostic interface is a more honest interface: it forces clarity through visual logic rather than relying on words that can be misread or mistranslated. Designing for the widest possible audience often produces the clearest possible product.
One of the biggest lessons was to market the benefits - not the features.
