🌿 NatureQuest AI: Turn Screen Time into Green Time with Open-Source AI

What if AI didn't ask you to spend more time on your screen—but inspired you to step outside?

NatureQuest AI is an AI-powered outdoor adventure application that transforms everyday nature exploration into fun, interactive missions. It encourages users to put their devices down, explore the world around them, observe nature, and build healthier digital habits.

This is my submission for the Hacktoberfest Open-Source AI Challenge — Week 1: Touch Grass.

---

🌱 1. The Problem: We Spend Too Much Time on Screens

We use technology for almost everything—learning, communication, entertainment, and work. But sometimes, scrolling through a screen replaces the simple experiences that make life interesting.

We might spend hours indoors without noticing the birds outside, the plants around us, or the small details of our environment.

I wanted to explore a different question:

Can we use AI to encourage people to spend more time in the real world instead of keeping them glued to a screen?

That question inspired me to build NatureQuest AI.

🚀 2. What I Built

NatureQuest AI turns outdoor exploration into a mission-based experience.

Instead of simply opening another app to scroll, users can discover a challenge, go outdoors, complete the activity, and track their progress.

✨ Key Features

• 🤖 AI-Powered Outdoor Missions: Generate nature-related activities and real-world challenges using an open-weight AI model.
• 🌳 Explore Your Surroundings: Discover activities involving plants, birds, trees, outdoor observation, and environmental awareness.
• 📸 Photo Evidence Verification: For missions that require visual evidence, users can submit a photo for verification.
• 🐦 Bird Sound Verification: Bird-observation missions can use recorded audio as supporting evidence.
• 🏆 XP and Rewards: Earn experience points, build streaks, and unlock badges through mission completion.
• 📔 Nature Journal: Keep track of discoveries and outdoor experiences.
• 📶 Offline-Friendly Missions: Use predefined missions when AI generation is unavailable.
• 🎮 Gamified Progress: Turn small outdoor activities into an engaging journey.

Feature note: Keep the photo and bird-audio features described as available only if their verification flow has been implemented and tested. Otherwise, label them as work in progress.

🔄 3. How NatureQuest AI Works

Here is the high-level user journey.

flowchart TD
    A["🌿 Open NatureQuest AI"] --> B["Choose or Generate a Mission"]
    B --> C["🤖 AI Suggests an Outdoor Challenge"]
    C --> D["🌳 Go Outside and Explore"]
    D --> E{"Does the Mission Require Evidence?"}
    E -- "Yes" --> F["📸 Photo or 🐦 Audio Evidence"]
    F --> G["🔍 Verify Evidence"]
    G --> H{"Evidence Accepted?"}
    H -- "No" --> I["Try Again"]
    I --> F
    H -- "Yes" --> J["Complete Mission"]
    E -- "No" --> J
    J --> K["🏆 Earn XP and Update Progress"]
    K --> L["📔 Record the Experience"]
    L --> M["Explore the Next Mission"]

The important idea is that AI creates the opportunity, but the real experience happens outside the application.

Evidence verification should be used only for relevant missions. Activities that do not require evidence should continue through the normal completion flow.

🧠 4. AI and System Architecture

NatureQuest AI is designed around an open-weight AI workflow for mission generation, with a separate application layer for mission management and progress tracking.

flowchart TB
    U["👤 User"] --> FE["Next.js + TypeScript Frontend"]
    FE --> API["FastAPI Backend"]
    API --> MS["Mission Service"]
    MS --> AI["Open-Weight AI Model"]
    AI --> MS
    MS --> VAL["Validate Mission Structure"]
    VAL --> FE
    FE --> OUT["Outdoor Activity"]
    OUT --> EV["Optional Evidence Submission"]
    EV --> VER["Evidence Verification"]
    VER --> COMPLETE["Mission Completion Logic"]
    COMPLETE --> XP["XP, Streaks and Badges"]
    XP --> JOURNAL["Nature Journal and Progress"]

What each layer does

Component	Responsibility
Frontend	Displays missions, progress, and the user interface
Backend API	Handles requests and application logic
Mission service	Organizes mission generation and mission data
Open-weight model	Generates outdoor mission ideas
Evidence verification	Evaluates relevant photo or audio submissions
Progress system	Tracks completion, XP, streaks, and badges
Nature Journal	Records the user's outdoor experiences

The exact inference provider and verification models depend on the implementation used in the final application.

🛠️ 5. Tech Stack

Technology	Purpose
Next.js	Frontend application
TypeScript	Type-safe application development
Tailwind CSS	Styling and responsive layouts
Python	Backend development
FastAPI	Backend API framework
Pydantic	Data validation and structured schemas
Gemma / another suitable open-weight model	AI mission generation
Ollama, if configured	Local model inference
Git and GitHub	Version control and collaboration

Important: Keep only the technologies and AI models actually used in your project. If you use a different model or inference setup, update this table accordingly.

🔓 6. Why Open Innovation Matters

Open innovation is important because developers should have choices in how they build and deploy AI-powered applications.

For NatureQuest AI, open-weight models create opportunities to experiment with mission generation, test different models, and explore local inference where the model and hardware support it.

Why I care about open-source AI

• Flexibility: Choose a model based on quality, speed, resource requirements, and licensing.
• Experimentation: Compare different models for generating practical outdoor missions.
• Deployment choices: Explore local inference or hosted deployment according to project requirements.
• Community contributions: Allow other developers to suggest missions, improve code, fix bugs, and extend the application.
• Greater control: Reduce dependence on one proprietary AI provider, depending on the chosen architecture.

Open-weight models do not automatically make an application free, completely private, or fully offline. Those properties depend on the model licence, deployment, hardware, data handling, and external services.

For me, the most interesting part is using open AI for something beyond another chatbot: encouraging people to reconnect with nature.

🌳 7. A Real-World Example

Imagine a user opens NatureQuest AI on a Saturday morning.

The application suggests a mission:

Mission: Become a Bird Observer 🐦

1. Go outside to a safe, accessible place.
2. Spend a few minutes quietly observing your surroundings.
3. Notice the birds and listen to the sounds around you.
4. If the mission requires it, record a short audio sample.
5. Submit the evidence for verification.
6. Complete the mission and earn XP if it passes the required checks.
7. Record the experience in your Nature Journal.

The activity is simple, but it encourages observation, curiosity, and time away from endless scrolling.

Evidence verification can help discourage unsupported completion claims, although an AI classifier cannot guarantee that every submission is genuine or correctly identified.

🎨 8. Design Philosophy

I wanted the interface to feel calm, natural, friendly, and inviting—not like a corporate dashboard.

The visual direction uses:

• Sage green and earthy colors
• Warm cream backgrounds
• Rounded cards and approachable layouts
• Clear mission instructions
• Visible progress and rewards
• Nature-inspired visual elements

The design supports the purpose of the application: make outdoor exploration feel accessible and enjoyable.

🧩 9. Challenges and What I Learned

Building NatureQuest AI helped me think about AI as part of a complete product, rather than just a model that generates text.

Some important engineering considerations include:

• Structured AI output: Generated missions need a predictable format that the application can validate.
• Reliable fallback behavior: Users should still have missions available if AI generation fails.
• Evidence quality: A photo or audio clip may be unclear, irrelevant, or insufficient for verification.
• Responsible gamification: Rewards should encourage outdoor exploration without making users feel pressured to stay in the app.
• Privacy: Camera and microphone access should be requested only when needed, with clear controls for reviewing and deleting evidence.
• Hardware limitations: Running an open-weight model locally depends on its size, quantization, and available system resources.

One lesson stands out: AI features are only useful when they support a meaningful user experience and work reliably within the limits of the system.

Before publishing, add one or two challenges you personally encountered and solved during development. Real examples make this section stronger.

🔮 10. What's Next?

NatureQuest AI can grow in several directions:

• 🌼 More mission categories for different ages and interests
• 🐦 Improved bird-sound recognition and clearer verification feedback
• 📷 Better image relevance checking
• 🌍 Optional location-aware missions with explicit permission
• ♿ Accessibility improvements for different users
• 🌱 Community-created mission packs
• 📊 Personal outdoor activity history and progress insights
• 🔋 Improved performance and offline support

These are potential improvements, not claims that all of them are already implemented.

Keep a record of outdoor experiences.

Replace these placeholders with real, publicly accessible image URLs. You can also embed a short demo video.

🎬 11. Live Demo

Try NatureQuest AI: https://drive.google.com/file/d/1E4YNQP3uqlSZSev_cjVn-vvIMQ2dOOsF/view?usp=sharing

If the application is not deployed yet, replace this section with a short video demonstration or remove it until the demo is available.

💻 12. Source Code

GitHub Repository: https://github.com/Rishabh-KSingh/NatureQuest-AI

The repository contains the project source code and implementation details.

If you are interested in open-source AI, nature-based applications, or creative uses of technology, feel free to explore the project and share feedback.

How to Contribute

Potential contributions include:

• Adding new outdoor missions
• Improving mission generation and validation
• Testing evidence verification
• Improving accessibility and mobile usability
• Reporting bugs or suggesting new features
• Improving documentation and setup instructions

Please follow the contribution instructions in the repository before submitting changes.

⚙️ 13. Run Locally

Use the repository's actual installation instructions if they differ from this example.

Prerequisites

• Node.js and the package manager used by the project
• Python and the project's required version
• Git
• Access to the configured AI model or inference service

Setup

# Clone the repository
git clone YOUR_GITHUB_REPOSITORY_URL

# Enter the project directory
cd YOUR_PROJECT_DIRECTORY

Install frontend and backend dependencies using the instructions and dependency files included in the repository.

Configure the required environment variables, then start the frontend and backend using the project's documented development commands.

Note: The commands above are a starting point, not a complete verified setup guide. Add the exact install, environment configuration, and run commands from your working repository before publishing.

💚 14. Final Thoughts

NatureQuest AI began with a simple idea:

What if we built AI that encouraged people to spend less time looking at screens and more time looking at the world?

I wanted to explore a positive use of technology—one that inspires curiosity, supports outdoor activities, and makes reconnecting with nature more engaging.

This project is my contribution to the Touch Grass challenge, and I hope it inspires other developers to experiment with open-source AI in creative, human-centered ways.

Technology doesn't always have to keep us online. Sometimes, it can give us a reason to step outside.

🌿 Build with AI. Explore with curiosity. Reconnect with nature.

I'd love to hear your feedback and ideas!

Hacktoberfest #OpenSourceAI #TouchGrass #NatureQuestAI #ArtificialIntelligence #OpenSource #NextJS #Gemma