Back

Forage · Wearable + AI · 2026

A wearable + AI system that turns fleeting inspiration into reusable design assets

Forage — Wearable + AI inspiration capture system
Role Product Designer · Systems thinking
Timeline 8 weeks
Scope 0→1 product definition · Hardware · Web app
Focus Capture-to-retrieval system for design inspiration

Overview

Design inspiration is high-signal but low-retention

Designers notice usable moments in the physical world but lose them before turning them into reusable material. Forage bridges that gap by capturing in context, translating raw input into structured design assets, and making retrieval a first-class product behavior.

Problem framing — fleeting moments vs. structured assets

The capture problem

Best inspiration happens mid-movement, in public spaces, or in passing moments too fast for manual capture. A wearable input surface makes the act of saving low-friction enough to happen in real time.

The translation problem

Raw captures are generic photos or notes. AI becomes the translation layer, classifying captures into usable asset types: images, color, typography, and motion.

The retrieval problem

Stored fragments are usually organized by file, not intent. The web interface indexes captures by type and recency, making them browsable and reusable instead of lost in a camera roll.

Solution

Four touchpoints. One complete system.

Forage works as a pipeline: capture in context, translate to design objects, organize into a structured library, and retrieve when building. The ring is the entry point; the system is the value.

System architecture — Sense → Capture → Translate → Organize → Reuse

Ring capture

A minimal wearable interaction lets designers save moments without interrupting their flow. Supports spontaneous capture away from a desk.

AI translation

The system classifies captures into four asset types and extracts reusable properties: dominant colors, typography characteristics, image subjects, animation references.

Structured library

A web app organizes captures by type and recency. Designers can browse, filter, and inspect captures in detail — transforming scattered moments into a personal inspiration channel.

Core Flows

From noticing to reuse in four steps

The strongest story is not capture alone. It is capture → interpretation → retrieval → reuse.

Ring capture mockup

Capture in context

The user notices a design-relevant moment and saves it with a minimal ring interaction. The value is speed and low disruption — supporting spontaneous capture outside desk-based workflows.

AI translation UI

AI translates the moment into a design object

The system classifies the capture and generates metadata depending on asset type. Raw input becomes categorized references: images, color palettes, typography characteristics, or animation references.

Web library browse interface

Browse and retrieve

The web app functions like a personal inspiration channel. Users can scan by recency, filter by asset type, and inspect captures in detail. Transforms scattered moments into a structured design library.

Reuse in design workflow

Reuse inside creative work

The capture becomes an input into later design work. Designers return to the library when building brand systems, moodboards, or motion studies, proving the system creates downstream value.

System

Forage works because it is a pipeline, not a feature

The value is not in any single screen. It is in how wearable input, AI interpretation, data structure, and retrieval behavior reinforce each other.

System diagram

Capture → Translation

Hardware reduces interaction cost; AI does the work a designer would otherwise do later — classify, extract, organize, and prepare for reuse.

Organization → Retrieval

Indexing by type and recency creates browsable structure. Users find captures when they need them, not lost in generic photo libraries.

Retrieval → Reuse

Making the library a first-class product behavior closes the loop. Designers actively reference past captures in their creative work.

Design Decisions

The decisions that made the concept cohere

Each decision came from identifying where the system was breaking or unclear.

Narrow to four output types

"Capture anything" is broad but weak. Limiting the system to images, color, typography, and motion makes the concept more teachable, more buildable, and more strategically coherent.

Ring as low-friction entry point

The wearable only works if it reduces interaction cost. Inspiration is often noticed mid-movement or in social settings where opening an app is too slow and too disruptive.

AI as translation infrastructure

AI is positioned as infrastructure, not a gimmick. It does the structural work a designer would otherwise do later: classify, extract, organize, and prepare captures for reuse.

Make retrieval as important as capture

Many concepts stop at acquisition. The stronger move was designing the web app as an inspiration repository with type filters, recency sorting, and browsable organization.

Design decision framework

Impact

Reducing the friction between noticing and reusing inspiration

Capture velocity

Ring interaction reduces friction enough that designers capture moments instead of letting them disappear. The act of saving becomes automatic.

Asset quality

AI translation converts raw captures into structured design objects. A photo becomes a color reference; a moment becomes an animation study.

Reuse integration

Organized library becomes a reliable reference in creative workflows. Designers return to past captures when building, extending their creative reach.

Success is measured by whether designers actively retrieve past captures during creative work — not by how many times they save.

Reflection

What the project clarified

Product definition over object design

The strongest part of this work is not the ring form factor. It is identifying the system failure — between noticing and reuse — and designing a pipeline to solve it. The wearable is simply the low-friction input surface for a larger system.

Retrieval as a first-class behavior

Most speculative concepts emphasize capture. The stronger move was designing the retrieval and reuse sides with equal rigor. The library interface became as important as the wearable.