iOS & Android app · Proof of concept for Madrid

Walk the city. Point your camera. Own the art.

Arteria is a mobile app that turns Madrid's galleries and street art into a guided experience: curated tours, a point-and-discover AR layer, and a marketplace to buy directly from the artists you meet along the way. This prototype walks through the real product, screen by screen — tap in below.

Walk through the app → Read the architecture
44screens prototyped
3experience paths
24Madrid stops mapped
Target locked
Prototype scope

This is a clickable HTML prototype — every screen is real markup you can navigate, none of it is a live backend. AR is simulated with a labelled "how this actually works" panel; payments, native AR and the CMS are specified, not built. See exactly what's real.

The brief, in one paragraph

Three curated paths, one marketplace, welded into a single loop.

Gallery tours, street art tours, and a point-and-discover AR layer — each built around Madrid's actual geography: Lavapiés, Doctor Fourquet, Malasaña, Reina Sofía. Every stop can lead straight into the artist's profile and, verified-purchase-gated, into a review. The architecture is city-agnostic from day one — Madrid is the first content pack, not a hard-coded assumption.

01 · CORE EXPERIENCE
Tours & AR

Gallery and street-art tours with live navigation, offline packs, and a two-pipeline AR layer — geospatial anchoring outdoors, image recognition indoors, with a guaranteed fallback ladder.

Try it →
02 · MARKETPLACE
Artists & artworks

Artist profiles, portfolio browsing, Stripe Connect checkout with Bizum and SEPA, and reviews gated to delivered orders only.

Try it →
03 · OPERATIONS
CMS & analytics

A full studio console — tour builder, artist roster, order management, review moderation, RBAC — plus the Firebase event taxonomy behind every metric.

Try it →
Research that shaped this build

Four findings that changed the architecture.

01
WebAR is a dead end for this product.

Niantic's 8th Wall — the default WebAR platform — is shutting down; hosted projects go dark in early 2027. The AR layer has to be native ARKit / ARCore.

02
Indoor and outdoor AR are different problems.

GPS doesn't work inside a gallery. Murals get geospatial anchoring; gallery pieces get image recognition. Two pipelines, one fallback ladder.

03
Stripe Connect, with Spain's actual rails.

Destination charges split payment to artists automatically. 21% IVA, SCA/PSD2, and Bizum — the payment method most Madrid shoppers actually reach for.

04
Madrid content is specific, and it shows.

Doctor Fourquet's 15 galleries in 600m², Tabacalera, the C.A.L.L.E. festival — real geography, not placeholder pins.

Read the full architecture →
The idea that welds it together

One journey, not two apps bolted together.

STEP 1
Walk the Lavapiés Walls tour
STEP 2
Scan the mural, AR reveals the making-of
STEP 3
Tap through to the artist's profile
STEP 4
Buy a signed print, Stripe splits the payout
STEP 5
Delivered order unlocks a verified review

This is the exact loop your analytics requirement is asking about — mapped event by event in analytics.html.

What's real in this build

44 screens you can click through today.

Native apps, live Stripe integration, a real backend, and production ARKit/ARCore code are not built — they're specified, in detail, in the architecture and estimate pages. Nothing here pretends otherwise.

Start the walkthrough → See the estimate