Case study - Mobile · Self-initiated side project
A field companion for plants you have to learn by name
Herbarium is a self-initiated side project: a mobile app that helps horticulture and garden-design students build, document and study a personal plant collection. It’s currently in the prototyping stage - not built, and not yet tested with real users.
Overview
01
Context
Study material scattered across multiple places.
Field identification of trees, shrubs and perennials is a core skill for horticulture and garden-design students, but the way most students actually practise it is fragmented: paper notebooks for field sketches, phone photos with no structure, voice memos that never get written up, and separate reference books or websites for the botanical facts that tie it all together.
By the time exam season arrives, a student's study material is scattered across multiple different places. Herbarium is a personal side project to explore whether a single, purpose-built app could hold the whole loop - capturing a plant in the field, and studying it later - without forcing students into generic note-taking or photo-organising apps that weren't designed for this workflow.
Capture in the field, study at the desk - currently two disconnected habits.
02
The problem
No tool combines fast field capture with structured, citation-backed reference data and a way to actively practise recall.
Students need one place to capture a plant in the field - photo, note or voice note, location - and later study it against reliable botanical facts.
03
Constraints
Named honestly - they're still open.
Discovery
04
Research
Informal and directional, stated plainly rather than dressed up.
- 01My own field observations - identifying and documenting plants outdoors, where the gap showed up firsthand: none of the tools I reached for were built for this loop
- 02Field trips - watching how people actually behave on site: hands full, poor signal, capture something fast and structure it later
- 03Conversations with garden-design students - informal interviews on how they study for identification exams and where their patchwork of tools breaks down
Notable findings
This research is informal and directional, not a formal usability study - appropriate for a side project at the concept stage, and given exactly that much weight.
05
Synthesis
Three needs that had to coexist in one product.
Capture, fast, in the field
Photo, voice and location logging with as little friction as possible.
Structure, after the fact
Turning a loose capture into a proper plant profile, cross-referenced against reliable botanical facts.
Recall, on demand
A way to actively test knowledge, not just re-read notes.
Never ask a student to do data-entry work a photo, a voice note or an existing reference source could already do for them.
Concretely: automatic transcription for notes, a shared public plant database instead of per-user redundant entry, and reference facts sourced from vetted publications rather than user-authored text.
Design
06
Spec before screens
The project started as a plain-text functional specification, refined iteratively in conversation with Claude before any visual design began - spelling out entities (plant profiles, families, groups), flows (uploading a list of plants to study, resolving ambiguous name matches, bulk photo recognition) and edge cases, before touching any screens.
Writing the spec this explicitly first - including open questions I hadn't yet resolved myself - made the later design decisions faster.
07
What changed once I prototyped it
Four parts of the brief that moved meaningfully.
Collaboration here is a solo-designer-plus-AI loop rather than a cross-functional one: Claude for structuring the spec and generating UI, ChatGPT for exploring copy and content ideas. There's no PM, engineer or fellow designer in the loop yet - a real limitation of a side project, and part of why developer expertise comes in before the build phase.
Current state
08
Discover & filter
A public database students browse and filter by height, family or group and plant status, with quick category chips - trees, shrubs, perennials, houseplants.
09
Field capture
A quick-add action - photo or video, voice note, or new plant - sits one tap away from anywhere in the app, backed by a native-feeling camera flow and a photo-upload component.
10
Voice notes with transcription
Recorded notes show a waveform, playback and an editable auto-transcript, with a visible nudge to double-check the botanical terms the transcription engine may have got wrong.
11
Locations on a map
Every recorded sighting can be plotted on a map, with a "closest to you" list for planning a field trip around what’s nearby. The map is also available on a plant detail page.
12
Plant profile
Each profile combines fixed reference photos and vetted botanical facts with the student’s own field photos, voice notes and written notes - public or private - in one place. Reference photography is organised into the categories that actually matter for identification: habit, leaf, flower, fruit, bark and leafless winter state, as tabs on the profile rather than one undifferentiated gallery.
13
Collection & practice
Beyond browsing the public database, students search and filter their own saved plants by name - Czech or Latin - or by notes, and jump into a practice hub that tracks progress through flashcard sets by group, like "shrubs flowering in spring", alongside quick links to their collection, plant families and the map of recorded locations.
What's next
14
The plan
In order, and no further than is honest.
15
Reflection
16