01
Overview
Pickahroo is a mobile-first harvest-sharing prototype designed to help tree owners share backyard harvests with nearby pickers. The product explores how a local food-sharing marketplace can make discovery, listing, booking, and owner review feel approachable for casual users.
The product also explores a common owner-side uncertainty: people may know a tree is producing fruit, nuts, or herbs, but they may not know what it is, whether it is useful, or how to describe it well enough to share. AI assistance helps owners turn that uncertainty into a safer, reviewable listing path.
This case study focuses on the Pickahroo product experience, not the separate Pickahroo AI Brand Operating System.
02
Product Problem
Many homeowners have fruit, nuts, herbs, or other backyard harvests that go unused because they do not have a simple way to share them. At the same time, nearby people may want local food but do not know where it is available, who owns it, or how to ask for access.
One barrier is identification. A tree owner may notice fruit or nuts on their property without knowing the variety, the best use, or whether anyone nearby would want it. Without help, the harvest may simply go unused.
The UX problem is not only “make a listing app.” The harder problem is trust. A harvest exchange involves someone’s property, food safety, timing, expectations, and personal boundaries.
03
UX Design Challenge
The prototype needed to make an unfamiliar exchange feel clear and trustworthy by answering:
- How do we support both sides of the marketplace without treating them as the same user?
- How do we give the owner enough control to feel safe participating?
- How do we help the picker discover food without encouraging trespassing or awkward access?
- How do we make permission and request review feel like part of the product, not friction?
- What information is needed before a listing feels credible?
- How can the product help an owner when they do not know what the harvest is?
- How can AI suggest a possible match without presenting itself as a final authority?
- How can the product help the owner decide whether the harvest is worth listing?
- What should a picker know before sending a request?
- When should pickup details be hidden until the owner approves?
- How can the product feel friendly without becoming careless?
04
Primary Users
Tree owner
A tree owner has access to a harvest-producing tree or plant, often on private property. They need help identifying or describing what is growing, deciding whether it is worth sharing, creating a listing, reviewing requests, and staying in control of pickup details.
Local picker
A local picker is looking to gather or buy local food nearby. They need to discover available harvests, understand what is being offered, request access clearly, and respect the owner’s boundaries.
05
Competitive Analysis: Falling Fruit
Falling Fruit is the clearest competitive reference because it is built around a collaborative map of the urban harvest. It helps people discover, edit, and contribute food-source locations, which makes it valuable for foragers and community mappers.
Pickahroo approaches the problem from a different angle. Instead of starting with the person who is out looking for food, Pickahroo starts with the person who owns or manages the harvest. The product asks: what if the tree owner knows something is growing, but does not know what it is, whether it is useful, or how to safely invite someone to pick it?
That difference changes the UX model. Pickahroo is not only a discovery map. It is an owner-led marketplace workflow. The owner can identify or describe a harvest, create a listing, review requests, and control when pickup details are shared.
Falling Fruit
- Collaborative food-source map
- Forager and contributor oriented
- Public discovery model
- Documents what is already findable or contributed
- Strong for exploration and community mapping
Pickahroo
- Owner-led harvest marketplace
- Tree owner and local picker oriented
- Request and approval model
- Helps owners identify, describe, and list harvests
- Strong for permission, trust, and controlled access
06
Design Response
AI-assisted harvest identification
AI assistance helps tree owners describe or identify a harvest when they know something is growing but are not sure what it is. The product treats this as a support layer, not a certification layer. Suggested identifications should remain reviewable, conservative, and clearly framed as possible matches.
Value translation for owners
The experience helps owners understand whether a harvest may be useful to someone nearby. Instead of requiring the owner to know market value, culinary use, or perfect naming before starting, the product helps them move toward a clearer listing that a picker can understand.
Owner-led marketplace model
Pickahroo brings the tree owner into the product as an active participant. The owner is not an invisible property holder behind a mapped food source. They can identify or describe the harvest, create the listing, review picker interest, and decide whether the exchange moves forward.
Permission-centered discovery
The picker experience is designed around request and approval rather than open access. This keeps discovery useful without treating private property as public inventory.
Role-Based Entry
The experience separates owner and picker paths early so users are not forced through irrelevant choices.
Simple Listing Creation
Owners can move from harvest details to a draft listing without managing a complex marketplace form.
Local Discovery
Pickers can browse available harvests in a way that emphasizes proximity, clarity, and practical next steps.
Request Before Access
The product keeps the exchange controlled by using booking/request language instead of exposing private pickup details too early.
Owner Review
Owners remain in control of whether a picker request moves forward.
AI as Support, Not the Main Character
AI assistance supports moments of uncertainty, such as helping owners describe or identify a harvest, but the UX does not treat AI as the authority. The primary experience remains human-centered marketplace coordination.
07
Product Experience Flow
Step 1
Tree Owner
Step 2
AI Harvest Assist
Step 3
Owner Listing
Step 4
Local Picker Discovery
Step 5
Request Review
Step 6
Approved Pickup Details
The flow helps owners move from uncertainty to a reviewable listing while preserving owner control and protecting private pickup information.
08
Trust and Safety Considerations
- Pickup details should not be public by default.
- The owner should control approvals.
- Product language should avoid overpromising certainty.
- AI-assisted identification should use possible-match language.
- The product should avoid presenting identification as certification.
- Uncertain or unsafe results should trigger conservative fallback behavior.
- Owners should remain responsible for confirming what they list.
- Pickup details should remain protected until request approval.
- The experience should make users feel guided, not pushed.
09
What This Demonstrates
- Persona-driven marketplace design
- Competitive analysis
- Permission-centered UX
- Owner-led marketplace strategy
- Local food exchange design
- Mobile-first product design
- AI-assisted identification UX
- Uncertainty handling
- Value discovery for non-expert users
- Responsible product language for AI suggestions
- Two-sided marketplace UX
- Role-based navigation
- Human-in-the-loop interaction design
- AI-supported uncertainty handling
- Prototype strategy
10
Reflection
Pickahroo is not just a harvest-sharing idea. It is a product design exercise in making a small, local exchange feel understandable, safe, and useful. The prototype shows how AI can support a workflow without taking over the user’s judgment or the product’s trust model.
The strongest product opportunity is not only connecting owners and pickers. It is helping owners recognize that something already growing in their yard may have value to someone else, then giving them a safe path to share it.
11 CTA