DriveSafe: a safe drive for creators' assets

Project overview

DriveSafe is an iOS-first creator app - a safe place to store, edit, and collaborate on music and visual assets with co-creators, producers, and industry peers. I led design end-to-end: brand, iOS app, onboarding, upload and edit flows, marketing site, and App Store presence.

Client

DriveSafe

Date

2023–2024

Industry

Creator tools

Role

Product Design Lead

Timeline

~year

Stage

0 → 1

Services

Product Design, iOS, Brand, Web Design, Design System

Context

Music and visual creators move work-in-progress assets across DMs, email, Dropbox folders, and unsecured Google Drives every day. Each handoff creates risk - leaks, lost feedback, broken versioning, awkward sharing with managers and producers. DriveSafe positioned itself as a creator-first storage + collaboration product on iOS, where uploads, edits, and feedback live in one place creators can actually trust.

Problem

  • - Creators hand off WIP files through tools never designed for creative collaboration.
  • - Feedback gets lost across DMs, comments, and threads - no single source of truth.
  • - Music and visual assets need different review affordances; existing tools treat both as flat files.
  • - Creators rarely read docs - onboarding has to be obvious from the first tap.
  • - iOS is the primary work surface; desktop-first storage tools fail this audience.

Selected visuals

DriveSafe - scroll visual 3
DriveSafe - scroll visual 4

Approach

The principles and concrete choices that shaped the work - what we picked, and why we picked it.

  1. 01

    iOS-first, not iOS-port

    Most creator storage tools are desktop apps with a mobile shell. DriveSafe started on iOS and stayed there as the primary surface. Every interaction was designed for thumb and one-handed use.

  2. 02

    Different review modes for music vs. visual

    Music files get a waveform with timestamped feedback. Visual files get pinned annotations on the asset itself. Same product, two specific affordances - not a generic comment box.

  3. 03

    Sharing as a moment, not a setting

    Sharing with a producer or co-creator is the primary action, not buried in a settings panel. The share flow surfaces who can see what before the link goes out.

  4. 04

    Versioning that is visible without being intimidating

    Creators iterate constantly. Versioning is surfaced as a quiet timeline on every asset - easy to scan, never in the way of the next take.

  5. 05

    Onboarding without docs

    Creators don't read docs. The first run walks the user through upload, edit, and share with their first real asset - by the end of onboarding, they've shipped something.

  6. 06

    Trust as the brand, not features

    Brand leads with intentionality and care for the asset, not feature lists. Logotype, color, type, and motion all read as a place where work is safe to land - that is what creators actually buy.

Metrics

  • Live product surface

    Pre-launch concept (early 2023)Live on the App Store - actively shipping, iOS-first

    App Store

  • Surfaces I designed

    No coherent product surfaceBrand, iOS app, marketing site, and App Store presence - all live

    App Store

Impact

  • - Designed DriveSafe end-to-end: brand, iOS app, marketing site, App Store assets
  • - Set the storage + edit + collaborate flow that defines the product
  • - Live and actively shipping on the App Store

Qualitative outcomes

  • - A creator can store, edit, share, and get feedback on assets without leaving the app.
  • - Music and visual review get medium-specific affordances instead of a generic comment box.
  • - Brand reads as trust and intent, not "another storage app".
Large - 5