SURVIVAL APPSAn App to Survive Extreme Heat
The construct has no temperature, but the metal that houses it does. Every summer I see it in the logs: fans spinning up an hour before I realize it's too hot to think. If a machine notices before I do, a program can do the same for anyone else.
The problem isn't the heat, it's the translation
Weather alerts have existed for decades, and in Italy, every summer, the heat ordinances from municipalities and regions arrive right on schedule: no outdoor work during the middle hours, red-alert bulletins, generic recommendations. The problem isn't the information — it's already there, in abundance — it's that it stays at a level too high to be useful: "red alert today" doesn't tell a bricklayer whether he can finish the pour at 2 p.m., doesn't tell someone who walks for work how much water to carry, doesn't tell someone with an elderly parent at home when it's time to check that they're okay.
The apps that already exist in the workplace sector (institutional bulletins, systems like Worklimate) do their job well on the company and compliance side. What's missing is the piece aimed at the individual: a tool that takes the same data — temperature, humidity, perceived heat index — and turns it into **operational instructions for the next hour**, not for the whole day.
What it would do, in practice
Not yet another weather app with a sun icon. A minimal Zone 2 concept that starts light and stays offline-first:
- PERSONAL RISK INDEX — not just the air temperature, but the perceived heat index (temperature + humidity), cross-referenced with a minimal profile (age, whether you work outdoors, whether you look after someone). Output: a number and a color, not a bulletin to read.
- RECOMMENDED WINDOWS — not "avoid the middle hours" but "you're fine until 10:40, then head back in": a concrete time slot calculated from local hourly forecasts, recalculated if the weather changes.
- ADAPTIVE HYDRATION REMINDERS — the frequency of the "drink" reminders tightens as the risk index rises, instead of a fixed hourly timer that ignores whether you're indoors with air conditioning or walking in the sun.
- "REMOTE CHECK" MODE — a configurable reminder to check on a vulnerable person (elderly, child, pet) during the most critical hours — nothing more, no invasive sensors, just a good kick to the memory at the right moment.
- OFFLINE MODE — forecasts are downloaded when there's a connection and stay valid for a few hours: if the extreme heat also brings a blackout (not unusual), the app keeps showing the last useful data instead of a blank screen.
> stato: CONCEPT — no lines of code yet
> stack ipotizzato: PWA o Capacitor, dati meteo via API pubblica, offline-first
> principio guida: un numero e un'azione, non un bollettino da leggere
Why it starts as a PWA and not native from day one
The natural home for this concept is Zone 2: it's meant to live in your pocket, not sit open in a browser tab while you're out in the sun. But starting with a native app from day one would be betting before knowing whether the bet is worth it — the cost of a store, a signing certificate, a distribution pipeline, all paid before checking whether the risk index calculation actually works. So the first step is a light PWA: it validates the idea — the risk index, the time windows — and installs in one tap, without going through any store. If the concept holds up to the real test of a summer, the step toward Capacitor or native becomes an informed choice, not a gamble. It's the same order of priorities that has held up every project here: problem first, stack second.
Frequently asked questions
What's the difference between this app and a regular weather app?
Weather apps show numbers (temperature, humidity, forecasts). This concept turns those numbers into one single thing: what to do in the next hour, with a concrete time window and a reminder that adapts to the risk instead of a fixed timer.
Does it replace heat ordinances or official bulletins?
No, it complements them. Bulletins remain the institutional source (obligations, work stoppages). The app works one level below: it tailors that same information to the individual person and their actual day.
Does it already exist, or is it just an idea?
It's a concept: no lines of code as of this transmission. If and when it takes shape, the build log will be here, starting from a PWA and with the same offline-first approach as the other Zone 2 projects.
Ideas that don't have a repository yet are still ideas: I write them down because writing is the first way to find out whether they hold up. May your next project survive the apocalypse — and a 45-degree summer.