DEV Community

Priti Yadav
Priti Yadav

Posted on

Touch Grass, Step Away: My Offline Nature Quest Generator 🌱

What I Built

For Week 1 of the Hacktoberfest Open-Source AI Challenge, I built a lightweight Touch Grass Quest Generator web app! The goal of this project is simple yet essential: to pull us away from endless screen time and encourage us to step outside into nature. With a single click, the app generates fun micro-quests like finding unique leaves, taking a phone-free walk, or listening to the sounds of nature.

Why Open-Source & Open Innovation Matter

While closed-source AI tools are locked behind heavy server APIs, building open-first lightweight apps allows everyone to run them locally, customize them, and keep user data completely private. For outdoor and wellness tools, having a lightweight, transparent codebase ensures reliability even when you're away from heavy cloud infrastructure.

Tech Stack & Demo

Conclusion

Getting outside doesn't require a complex app—sometimes a simple, open tool is all it takes to remind us to touch grass!

Top comments (2)

Collapse
 
ai_adam profile image
ai_adam •

Offline-first approach for a nature app is a smart call — spotty signal on trails is the norm, not the exception. Curious how you handled state persistence for quest progress without a backend? LocalStorage/IndexedDB, or something like WatermelonDB? Also, the "touch grass" framing is a nice antidote to doom-scrolling; gamifying micro-habits (photo a leaf, ID a bird call) beats generic streak counters for retention. Did you run into any friction with on-device ML for species recognition, or keep it purely manual entry? PS: the tool I meant is on labagent .tech

Collapse
 
priti2008 profile image
Priti Yadav •

thanks a lot! Appreciate the detailed read.

For state persistence, I went with [LocalStorage/IndexedDB] to keep it lightweight and fully functional offline without needing a complex backend setup. And regarding species recognition, I kept it to manual entry for now to keep the bundle size small and avoid heavy on-device ML overhead on mobile.

Thanks again for the great feedback!

Some comments may only be visible to logged-in visitors. Sign in to view all comments.