Specimen: TreeGo
Category: Product Design / Location-based App / Nature Exploration
Platform: iOS / Android
Focus: Mission / Pioneer / Echo / Seed / Verification / Oracle
Worldview: Trees are the protagonists; players are witnesses
Role: Solo Product Creator / UX / UI / Frontend / Backend / Launch

TreeGo

“Some trees are lonely. Until someone notices.”

TreeGo is one of my clearest examples of turning a soft, easily-forgotten behavior into a durable product system. I was not trying to build a plant encyclopedia. I was trying to build a product that makes people go outside, notice trees, and keep returning to the urban forest over time.

Its starting point was simple: many people are not uninterested in nature. They just do not know how to begin observing it, or how those observations can accumulate into something meaningful. TreeGo translates that ambiguity into guided, rewarded, and verified actions.

TreeGo mission cards — **Figure 1**Mission cards make the goal concrete. Instead of facing a blank map, users immediately see which species matter this cycle, how Pioneer and Echo differ, and what rarity means in reward terms.

What mattered most to me was how to turn “noticing” into a structured behavior rather than a one-off check-in. That is why TreeGo uses two loops together: Mission Mode for guided discovery, and Seed Mode for open-ended exploration.

In Mission Mode, users see featured species that rotate every two weeks. The first person to find one becomes the Pioneer and gets a stronger reward. Others can then visit the existing point and complete an Echo. This creates first-discovery value without making the system useful only to the first player.

TreeGo map — **Figure 2**The map reorganizes the city into an explorable forest. Missions, existing tree points, pending seeds, and player position all live in the same spatial system.

Seed Mode is equally important. It is not just a side feature outside the mission flow. It is how the world grows. Players can record species they already recognize and leave behind hint points that may later become part of mission-based discovery.

Many of TreeGo’s rules exist to handle real-world constraints rather than abstract game balance: Echo requires being within 20 meters, the same species cannot be duplicated within 50 meters, only public and grounded plants are allowed, and GPS, photography, AI recognition, and community verification all work together to protect trust.

TreeGo species detail and check-in action — **Figure 3**The species detail screen connects knowledge to action. It does not only identify a tree; it lets users read, confirm, and continue the exploration from the same place.

Another major design layer was identity. I did not want TreeGo to feel like a list of collected items. So the app uses both pts and rpt: one for exploration traces, the other for social credibility within the community.

Figure 4The profile screen turns exploration into identity: level, points, Pioneer / Seed / Echo statistics, and membership state all accumulate into a recognizable explorer role.

The achievement system follows the same thinking. Instead of rewarding only volume, TreeGo also tracks rain, night, low temperature, long-distance movement, and regional variation. That encourages re-experiencing the city through different conditions.

TreeGo achievement wall — **Figure 5**Achievements and unlock moments turn observation into memory. The woodcut badge language also keeps the reward system tied to the product’s natural theme rather than generic gamification.

TreeGo badge unlocked moment — **Figure 5**Achievements and unlock moments turn observation into memory. The woodcut badge language also keeps the reward system tied to the product’s natural theme rather than generic gamification.

I also did not want TreeGo to stop at education or record-keeping, which is why I added Plant Oracle. On the surface it is a Pro feature and a playful extra, but deeper down it gives encounters with plants emotional texture and memorability.

TreeGo Plant Oracle — **Figure 6**Plant Oracle adds a layer of poetic interpretation without replacing recognition or exploration. It gives the system a lightly mysterious emotional register.

The Dex completes the structure. Missions help people begin. The map drives movement. The Dex organizes accumulation. Oracle adds emotional residue. Verification protects quality. Together these layers make TreeGo feel internally coherent rather than feature-based.

TreeGo Dex screen — **Figure 7**The Dex places known and unknown species in one index, giving exploration a durable structure and making absence just as motivating as completion.

If I had to summarize what matters most about TreeGo, it would be this: I took an abstract value proposition and translated it into missions, distance rules, data structures, rewards, verification, identity, and emotional tone until it became a real product system.

Like my other independent apps, this one was also built end to end by me: product framing, exploration logic, map interactions, seed and verification flows, encyclopedia content, visual system, frontend, backend, subscriptions, support pages, and launch.

TreeGo is not just plant data inside an app.
It is a system for redesigning how people learn to notice trees again.

TreeGo

How I turn ideas into products

Explore how I approach products, systems, clarity, and growth through six questions.