Platform systems

DESIGNING A SYSTEM BETWEEN CAMERA & STORY

Platform promise

A GoPro experience does not end at the shutter. It continues through connection, control, capture, transfer and storytelling.

Platform promise

A GoPro experience does not end at the shutter. It continues through connection, control, capture, transfer and storytelling.

The promise

The product is not only the camera. It is the connective experience that helps a person get from a captured moment to a story worth sharing.

That promise crosses hardware and software boundaries: discovering a camera, establishing trust, controlling capture, moving media and continuing into Quik or an adjacent creator workflow.

Evidence interviewConfirm the customer moment that made this continuity most important and the concrete consequence when it broke.

The platform

Different clocks.One continuous experience.

Multiple camera generations, software surfaces, release cadences, disciplines and system states had to read as one product without hiding the real boundaries between them.

Fig. 01 — The bounded platform modelStatic first · motion deferred

CameraCapture state

ConnectionTrust + recovery

ControlReady + recording

QuikTransfer + choose

StoryCreator surfaces

Clock A

Hardware generations create long-lived constraints.

Clock B

Apps, services and launch work move at different speeds.

System state

Every handoff must explain what is happening and how to recover.

Three decisions

Design the handoffs,then make them reusable.

Make connection and device state understandable and recoverable.
The chooser makes the first platform handoff visible: a person can identify the camera, understand readiness and know the next action. Confirm the failure states, rejected alternative and recovery evidence before publication.

Fig. 02 — Connection is a product state, not a setup footnote.
Fig. 03 — A multi-modal language connects global principles to surface-specific components.

Establish a reusable language across hardware and software.
The system preserves shared principles while allowing web, native app, camera and desktop environments to respond to their own constraints.
Turn repeated launch work into shared patterns and alignment tools.
Successive camera generations became a test of continuity: the team could carry forward recognizable patterns while making room for new capability. Confirm where the pattern reduced rework or changed a decision.

Fig. 04 — Launch evidence across a changing camera family; a launch list alone is not impact.

Platform breadth

The connective system had to support more than one flagship flow. These artifacts show how the platform language extended into capture configuration, creator programs and professional exploration.

Three GoPro interface studies for browsing, adding and applying camera presets — GP.01 — Camera presetsProves the language can translate complex capture settings into reusable choices.

GoPro Awards submission and challenge interfaces across several web screens — GP.02 — GoPro AwardsProves platform breadth beyond device control into a creator-facing submission workflow.

Tablet concept controlling four GoPro camera feeds in one interface — GP.03 — Multi-camera explorationProves how camera state and control patterns could scale to a professional, multi-device context.

Impact

What changed for customers,delivery and the organization?

Customer

Confirm a bounded outcome for connection, control, capture or transfer.

Delivery

Confirm what became faster, more reliable or easier to ship across launches.

Adoption

Confirm a measured behavior or a specific qualitative signal and its time window.

Publication gateDo not replace these prompts with inferred metrics. Camera launches, titles and artifacts are evidence of scope—not proof of impact by themselves.

Ownership

The final case must separate what I framed, decided, influenced, facilitated and personally delivered.

Framed: The connective experience as a platform problem spanning camera and software state.
Led: UX design for the wireless connectivity layer of Quik; exact title and dates remain provisional.
Built with others: A multi-surface system and alignment tools across UX, Engineering and Creative; confirm collaborators and decision rights.
Delivered: Connection, control and capture work plus the visible artifacts shown here; confirm the precise shipped set.

Reflection

The platform made continuitya design material.

The strongest outcome was not a single interface. It was a way to reason across a changing camera family, the Quik relationship and adjacent creator surfaces.

Before publishingConfirm what the platform enabled, what did not work, and what Mario would evolve next.

A triangular doorway in dark stone with a slit of white light

Next case — not selectedCase 03

Static narrative v1. Motion and the interactive signal path begin only after story and evidence approval.