Case study · TrailTimes

Ten App Store screens,
composed by an agent.

TrailTimes is a trail-riding app with live trail matching and leaderboards. It needed a full iOS set: a connected panorama across the first three screens, and seven more that show the product actually doing something.

Every device screen here is the real app, running against real trail data in Cumberland, BC. No mockups, no placeholder times.

TrailTimes and AssetShip are built by the same company. This set had nowhere to hide: it went to the App Store under our own name, so every rough edge in the tool had to be fixed before the listing could ship.

TrailTimes App Store screen 01TrailTimes App Store screen 02TrailTimes App Store screen 03
iPhone 6.9″ · 1320 × 2868
Screens
10
Export size
1320 × 2868
Store sizes, one scene
4
Revision rounds
7
The shipped set

Ten screens, in carousel order

Each one answers a question a browsing rider is already asking. The copy on the phone is the product’s own — trail names, split times and elevation straight out of the app.

  1. Every trail. Every second. — TrailTimes App Store screen 01
    01

    Every trail. Every second.

    Opening frame

  2. Watch the trail tick up as you ride — TrailTimes App Store screen 02
    02Live trail matching

    Watch the trail tick up as you ride

    Vanilla, 56% — live against a personal best

  3. See where you stack up — TrailTimes App Store screen 03
    03Trail leaderboards

    See where you stack up

    A real board, real times

  4. Every trail around you — TrailTimes App Store screen 04
    04The trail map

    Every trail around you

    The Cumberland network

  5. Know the trail before you drop in — TrailTimes App Store screen 05
    05Trail detail

    Know the trail before you drop in

    Bear Buns Climb — 2.26 km, 231 m of gain

  6. See exactly where you went — TrailTimes App Store screen 06
    06After the ride

    See exactly where you went

    An 8 km lap over thirteen trails

  7. Every trail you finished, logged — TrailTimes App Store screen 07
    07Trail completions

    Every trail you finished, logged

    One trail live, one already done

  8. Plan the loop, see the climb — TrailTimes App Store screen 08
    08Route builder

    Plan the loop, see the climb

    Seven waypoints, closed into a loop

  9. Take the map with you — TrailTimes App Store screen 09
    09Offline maps

    Take the map with you

    Caught mid-download, cell 2 of 3

  10. Every ride, in one place — TrailTimes App Store screen 10
    10Your profile

    Every ride, in one place

    Stats, history, achievements

Connected artboards

One photograph, cut across three screens

The App Store shows screenshots side by side as a reader swipes, so the first three share a single backdrop. Group the artboards and the image spans the group — each export gets its own slice, aligned to the pixel, at every store size.

The backdrop was generated in the editor from a written brief, at high resolution. On a Pro plan that is a rounding error against the monthly credits.

Panorama panel 01Panorama panel 02Panorama panel 03
Model Context Protocol

The whole set was assembled in a conversation

No editor session was required to produce it. AssetShip exposes the editor over MCP, so an agent can compose, review its own renders and export — and you open the editor only when you want to touch something yourself.

create_project

A project and a starter scene, from one line of intent.

generate_backdrop

A mountain-biker backdrop from a written brief, spanning the first three artboards.

upload_image

Real captures dropped into the device frames — by URL or straight from base64.

edit_scene

Headlines, eyebrows, backgrounds and device screenshots, applied as a batch of commands.

render_preview

The agent looks at what it just made, and adjusts before anyone else sees it.

export_screenshots

Every artboard at exact store resolution, returned as download URLs.

Version history

The set changed seven times after it was “done”

A trail name got swapped for a friendlier one. The offline screen was re-shot mid-download. The activity screen went from a four-minute ride to a proper 8 km lap. Each round is a snapshot you can name, and step back to.

A finished set is exactly the point at which you stop wanting to touch it — so restoring is itself snapshotted first, and rolling back is never the thing that loses your work.

Project history
  1. Shipped App Store set (10 screens)
  2. Before re-capture (attribution + trail-fit + offline)
  3. English v2 — collapsed attribution, trail fit, offline download
  4. English v3 — offline redesign (dark map, bottom drawer, shape draw)
  5. English v4 — Vanilla trail + restyled offline picker
  6. English v5 — offline download in flight
  7. English v6 — 8 km Cumberland lap on the activity screen
  8. English v7 — trail card framed, route loop, long ride
  9. Before restoring “English v7”
Export

Ten artboards, about four seconds

One scene renders to every size the stores ask for. The renderer is deterministic — the same scene gives the same bytes, so a re-export after a one-word change is a diff you can trust, not a re-shoot.

Localised variants come from the same scene too: translate the headlines once and every locale exports as its own foldered set.

  • iPhone 6.9″1320 × 2868
  • iPhone 6.5″1284 × 2778
  • iPad 13″2064 × 2752
  • Android phone1080 × 1920

Your set, the same way

Start in the browser for free, or point your agent at the MCP endpoint and describe what you want. Pro adds the AI credits, cloud sync and version history this project ran on.