🌿 OuttaDoor: Turning Everyday Life Into an Adventure

Aditri — Sat, 10 Oct 2026 19:15:00 +0000

What I Built:-

🌿** OuttaDoor **— Turning Everyday Moments Into Outdoor Adventures

What if technology encouraged us to spend less time on screens and more time experiencing the world around us?

That idea inspired OuttaDoor, a web application designed to turn ordinary moments into opportunities for outdoor adventures.

Users can choose an outdoor vibe, such as Nature, Walking, Photography, or Friends, select their available time and mood, and generate a quest to help them get outside and try something different.

The idea is simple: make the screen the starting point, not the destination.

I built OuttaDoor for people who sometimes need a little inspiration to break their routine, explore their surroundings, or enjoy a small outdoor activity.

Demo
🌐 Live Website: https://outtadoor-1.onrender.com/

The application is deployed on Render, and I've tested the live website independently of my laptop.

Code
💻 GitHub Repository: https://github.com/aditric7/OuttaDoor

The repository contains the frontend, backend, and project documentation.

Tech stack:

1:HTML, CSS, and JavaScript for the frontend
2:Python, FastAPI, and Pydantic for the backend
3:Gemma 3 1B through Ollama for the local AI setup
4:Render for deployment

How I Built It

I worked on setting up the project structure, connecting the frontend to the FastAPI backend, configuring deployment, troubleshooting issues, updating the README, and testing the live application.
For the AI component, I explored using Gemma 3 1B through Ollama, allowing the model to run locally in my development setup.
The backend attempts to use the configured Ollama service to generate quests. I also implemented a fallback mechanism so the application can return predefined quests when the AI service is unavailable.

**One important limitation in the current deployment **is that the Render backend cannot automatically access the Ollama model running on my laptop. Consequently, the deployed website may return fallback quests rather than generating them through Gemma.

I also used AI assistance during development. While working through the project setup, integration, configuration, debugging, deployment, and testing process myself. This project helped me understand how the different parts of a deployed web application fit together.

Why Does Open Innovation Matter?

Open-weight models offer developers an opportunity to experiment with AI beyond simply calling a closed, hosted API.

By exploring Gemma 3 1B with Ollama, I could learn about local inference, experiment with the model in my own environment, and understand the practical trade-offs involved in running AI locally.

A locally running model can offer more control over where inference happens and reduce dependence on a remote inference service when configured appropriately. It also provides flexibility to experiment with different models and deployment approaches.

However, local inference requires suitable hardware and a running model service. In my current deployment, the local model is not automatically available to the hosted backend, which is why the fallback mechanism matters.

For me, open innovation made the AI implementation a learning experience—not just about using a model, but also about understanding how it runs, how the application connects to it, and what happens when the model is unavailable.

My Agent Session:
I don't currently have a DevRelay agent session to share. I developed the project with AI assistance and hands-on configuration, integration, debugging, deployment, and testing.I'll make one soon.

Prize Categories:
Potential category to consider: Gemma — Best Use of Gemma.

Prize Categories
I'm interested in the Gemma category because I explored Gemma 3 1B through Ollama for local quest generation. I'll make sure my submission accurately reflects how the model is implemented and used in the project.

✨ What Works Today?

1: A web interface for generating quests
2: A FastAPI backend connected to the frontend
3: A fallback mechanism for when the local AI service is unavailable
4: A deployed website that I tested independently of my laptop

🚀 ** What I'd Improve Next**

I'd like to make model inference available in the deployed version, improve quest personalization, and explore ways to make the experience more useful for different outdoor activities.
Building OuttaDoor has been a learning experience in turning an idea into a working, deployed application—not just writing code, but connecting components, debugging, and testing the result.
Try OuttaDoor: https://outtadoor-1.onrender.com/

*If you try it, I'd delighted to hear what you think! *🌿

🌿 OuttaDoor: Turning Everyday Life Into an Adventure

Aditri — Sat, 10 Oct 2026 19:00:24 +0000

We use technology for almost everything, but what if we built something that encouraged us to step away from our screens?

That question inspired 🌱OuttaDoor, a quest-generation web application designed to turn ordinary moments into opportunities for real-world adventure.

🔗 Live Demo: https://outtadoor-1.onrender.com/
💻 Source Code: https://github.com/aditric7/OuttaDoor

🌱 The Idea Behind OuttaDoor

Sometimes, all we need is a small idea to break our routine: explore somewhere new, try an outdoor activity, or spend time doing something different.

OuttaDoor is designed to make that first step easier by generating quests that encourage users to engage with the world around them.

The idea fits the Hacktoberfest Week 1 theme, “Touch Grass,” by making the screen a starting point rather than the destination.

🛠️** How I Built it:--**

I built the application using:

1:HTML, CSS and JavaScript for the frontend
2:Python, FastAPI and Pydantic for the backend
3:Gemma 3 1B with Ollama for the local AI setup
4:Render for deployment

I worked on setting up the project structure, connecting the frontend and backend, configuring deployment, troubleshooting issues, updating documentation, and testing the live application.

I also used AI assistance during development. Along the way, I worked through the integration and deployment process to understand how the different parts fit together.

🤖 Why Open-Weight AI?

I explored running Gemma 3 1B locally through Ollama. This gave me an opportunity to learn about local inference and the flexibility of working with open-weight models.

A local model can offer more control over where inference happens and can reduce dependence on a remote model API when it is running on your own machine.

I also deployed the application on Render and implemented fallback quest generation so the website remains usable when the local AI service is unavailable.

There is an important limitation in my current deployment:
But the Render backend cannot automatically access the Ollama model running on my laptop. When that model is unavailable, the application falls back to predefined quests. So the live demo does not always perform AI inference.

✨ What Works Today?

1: A web interface for generating quests

2: A FastAPI backend connected to the frontend

3: A fallback mechanism for when the local AI service is unavailable

4: A deployed website that I tested independently of my laptop

🚀 ** What I'd Improve Next**

I'd like to make model inference available in the deployed version, improve quest personalization, and explore ways to make the experience more useful for different outdoor activities.
Building OuttaDoor has been a learning experience in turning an idea into a working, deployed application—not just writing code, but connecting components, debugging, and testing the result.
Try OuttaDoor: https://outtadoor-1.onrender.com/

*If you try it, I'd delighted to hear what you think! *🌿

DEV Community: Aditri

🌿 OuttaDoor: Turning Everyday Life Into an Adventure

🌿 OuttaDoor: Turning Everyday Life Into an Adventure