Jacket?

Jacket? answers one question. You open it, and it says YES or NO. No dashboards. No radar map. No fourteen-day outlook you were never going to read. One word, the size of the screen, and a single line telling you why. HOW IT DECIDES It looks at the next six hours where you actually are, not the city average, and checks four things in order: • Rain now, or likely soon, while it is still cool • The coldest it is going to feel in that window • How cold it feels right now • Wind over 20 mph with a chill on it The first one that trips gets you a jacket, and the reason line tells you which one it was: "Drops to 52 by 6pm", "Rain likely around 4pm", "Windy — 23 mph". RUNS HOT? RUNS COLD? One slider, eight degrees in either direction. The app shows you the cutoff it landed on — "You run cold — jacket below 68" — and re-answers the moment you let go. BUILT TO OPEN AND CLOSE AGAIN • The answer is on screen before the network replies, from the last reading • Works with no signal: shows the cached verdict, stamped with when it was taken • Colour tells you before the text does — blue for jacket, amber for not • TalkBack reads the verdict and the reason as one sentence • Six-hour bar chart underneath, if you want to see the shape of the day • Phone and tablet WHAT IT DOES NOT DO No account. No sign-up. No ads. No analytics. No tracking. No third-party SDKs of any kind — the app talks to exactly one server, the weather API, and nothing else. It does not even use Google Play Services: the location fix comes from the Android framework, so it runs on a de-Googled device. Only coarse location is requested. It is used to fetch the forecast for where you are standing, and for nothing else. It is never attached to an identifier, never stored on a server, and never sold. One dollar, once. That is the whole business model. Forecast data is from MET Norway, the Norwegian Meteorological Institute, published under CC BY 4.0 and credited in the app.