Muwaffaq
← All work

Skyline

A weather app that answers in seconds

TL;DRI designed and built a weather app around one order, now, next and later, so a visit takes seconds. A rule engine shows only the card that matters, and the rules people rely on are unit-tested.

SkylineA weather app that answers in secondsCompleted · App
Role
Design and build
Timeline
Oct 2026
Tools
React, Vite, Open-Meteo, Vitest
Result
One screen that answers now, next and later, with a demo for every weather

The problem

Weather data is everywhere. The problem is weather apps that show too much at once, bury the forecast behind screens and use charts you have to interpret. Skyline was built from a written brief with one goal: speed of comprehension. A successful visit can last three to five seconds: open it, see 24°C and rain likely around 10 AM, take an umbrella, close it.

Everything follows one order: now, next, later. Now is the temperature, condition and high and low. Next is the coming hours. Later is the next five days. Anything outside that order has to earn its place.

One screen, read in seconds

Clear day: the temperature first, then one card that matters, here a UV warning
Clear day: the temperature first, then one card that matters, here a UV warning
Rain: the brief says when it starts, and the rain hours are highlighted
Rain: the brief says when it starts, and the rain hours are highlighted
Storm: the warning outranks everything else
Storm: the warning outranks everything else
Night: the page turns to ink, with the best time to be outside
Night: the page turns to ink, with the best time to be outside

Only the card that matters

A rule engine picks which card to show, in priority order, so the screen never stacks five warnings:

PriorityCardShown when
1Storm or heavy rainA storm, or a 70% chance of rain within 3 hours
2Rain windowTwo or more hours in a row at 50% or more: "Rain likely 4–6 PM"
3UVUV index 6 or higher
4WindWind of 35 km/h or more
5Temperature dropA drop of 5° or more within 3 hours
6Best time to be outsideThe nicest window in the next 12 hours
7Compared with yesterday2° or more warmer or cooler than yesterday at this hour
8CalmNothing else applies

A one-line brief under the city sums it up the same way: "Clear now, high of 29°."

Key decisions

DecisionWhyWhat it cost
One screen, no tabsThe questions people ask a weather app fit on one scrollNo radar, maps or detailed charts
One forecast request, cachedOpens instantly and still shows the last forecast offlineData can be up to one refresh old
A demo mode for every weatherStorms and snow are rare; every state has to be designable and testable on any dayA second, synthetic data path to keep in step
Location is used once and never stored on a serverPeople shouldn't trade privacy for a forecastNo sync between devices

The restyle

Left, the first version: blue gradients and frosted glass. Right, the restyle: ink on paper, a giant display numeral, mono labels and solid cards. The look takes cues from (Not Boring) Weather.
Left, the first version: blue gradients and frosted glass. Right, the restyle: ink on paper, a giant display numeral, mono labels and solid cards. The look takes cues from (Not Boring) Weather.
Left, the first version: blue gradients and frosted glass. Right, the restyle: ink on paper, a giant display numeral, mono labels and solid cards. The look takes cues from (Not Boring) Weather.

Tested where it matters

The rules people rely on have unit tests with Vitest: the card priorities, the rain window, the best time to be outside, the comparison with yesterday, the data clean-up and the sky logic. The code is public on GitHub.

What shipped vs what was designed

Built and working as a web app with React, Vite and Open-Meteo, with a demo for every weather. It isn't published to the app stores, and there are no usage numbers.