If you’ve ever tried to book a photographer while traveling abroad, you know the user experience is usually terrible. You are stuck scrolling through scattered Instagram hashtags, navigating clunky personal websites, and sending cold emails hoping someone speaks your language and actually has availability.
It is a fragmented, frustrating process for something that should be a highlight of a trip. We realized there was no standard, trusted marketplace specifically designed for this.
So, we decided to build one: Picturo.
Our purpose was simple: create a single, unified platform that connects international travelers directly with vetted, professional local photographers in key destinations like Athens and Rome. But from a product perspective, we had to think carefully about how this platform should actually feel to use.
Here is a look at how we approached building Picturo and why we decided a Single Page Application (SPA) was the only way to go.
Designing for a Visual-First Experience
When you are building a photography marketplace, the visual experience is everything. The product isn't just the code; it’s the stunning imagery our photographers produce.
We knew our users would need to:
Browse massive grids of high-resolution portfolio images.
Dynamically filter photographers by destination, dates, and distinct editing styles.
Move effortlessly from browsing galleries into a multi-step booking and checkout flow.
If we went with a traditional multi-page architecture, every time a user clicked a new photographer's profile or applied a filter, the browser would have to do a full page reload. In a highly visual app, that brief flash of a white screen and the jarring reload completely breaks the immersion. It makes a modern marketplace feel like a directory from the early 2010s.
Why an SPA? Pure Fluidity
We wanted Picturo to feel like a premium native app right in the browser—buttery smooth and entirely uninterrupted. A Single Page Application was the obvious choice to achieve this.
By building an SPA, we could completely decouple the user interface from the server's routing. Once the initial application loads, everything happens fluidly on the client side.
Seamless Browsing: Users can hop between different photographer portfolios in Athens or Rome instantly. The navigation shell stays locked in place, and only the gallery content swaps out, making the browsing experience incredibly fast.
Stateful Checkout: When a user finds a photographer they love, they enter the booking flow. Because it’s an SPA, we can manage their booking state perfectly across different steps without worrying about dropped connections during page reloads.
Interactive UI: Features like our destination Q&A sections and dynamic image carousels feel instantaneous and highly responsive.
The Takeaway
Building Picturo has been an incredible journey in matching architectural choices directly to the desired user experience. We realized early on that when your core product is visual art, the technology delivering it needs to get out of the way entirely.
The SPA architecture allowed us to build a marketplace that isn't just functional, but genuinely enjoyable to browse, keeping the focus exactly where it belongs: on the incredible work of our local photographers.
Have you built a visually heavy platform recently? I'd love to hear how you approached the balance between functionality and user experience in the comments!
