Outside Hour: a local Gemma model that wants you off your phone in 60 seconds

Description and use

Outside Hour uses a local Gemma model and open data to recommend a nearby outdoor spot in 60 seconds, display direction, return time, and items to bring, then enforces a phone‑down screen.

Problem

Users often scroll through multiple “get outside” apps before deciding where to go, wasting attention and time.

Outcome

The app delivers a concise, data‑driven outdoor plan within 60 seconds, reducing decision friction and encouraging users to leave their phones behind.

Workflow

• 1. User enters current location and desired duration. 2. App queries Overpass API for nearby named parks, gardens, water bodies, viewpoints and footpaths. 3. App queries Open‑Meteo for forecast, sunrise, sunset, air quality. 4. Code computes walking time, straight‑line distance, bearing, turn‑back time, and light conditions. 5. Gemma 4 E2B‑it selects one place from the fetched list and writes a pocket card. 6. App displays a 60‑second ring timer while the page is visible. 7. When time expires, ring turns red, page dims, and a phone‑down screen shows the turn‑back time and elapsed/away times. 8. User can print the pocket card or add a calendar event with an alarm for the turn‑back time.

Evidence

Outside Hour gives itself 60 seconds of your attention, and shows it: a ring in the corner counts down while the page is on your screen.

Source

A Gemma model running on my laptop picks one real park, lake or garden nearby and writes a pocket card.

Source

The meters are honest about what a web page can know. They use the browser's Page Visibility API: time counts only while the page is visible.

Source