I built a live Earth wallpaper for Windows

BB — Fri, 02 Oct 2026 02:26:40 +0000

For months my desktop background was the same photo. Fine image. Never changed.

I kept wishing the map behind my icons would track the real sun — day side bright, night side with city lights — and show times for a few cities I actually care about. Not another floating widget pack. Just wallpaper that behaves like Earth.

So I built Orblune, a live Earth wallpaper for Windows 10/11.

Try it: https://cbybb.github.io/Orblune/

Code: https://github.com/CByBB/Orblune

I’m CByBB on GitHub (also CodeByBB / BB / B.B. depending on the account). This is article 01 in a short series about making Orblune — what worked, what fought back, and what’s next.

What Orblune does (the short list)

Flat Earth map as wallpaper under your desktop icons
Day/night from real sun position
City cards with local time
Weather on those cards (MET Norway)
Optional map themes if you unlock Premium
Multi-monitor: turn screens on/off, theme per display when Premium

Free tier is usable. Premium is a one-time unlock, not a subscription. I built the free path first so I could run it myself every day.

Challenge 1: Windows doesn’t want you here

The UI is a Tauri WebView. The painful part is hosting.

On Windows, live wallpaper usually means parenting your window into Explorer’s WorkerW layer. Docs for that are mostly blog posts and old forum threads. My first builds either:

sat on top of icons (useless), or
attached once, then died after a display sleep, or
“fixed” themselves by reattaching every few seconds and making the taskbar flicker

I learned the hard way that sending Progman’s magic 0x052C message too often flashes the whole desktop. So I started caching the WorkerW handle and only spawning it when it’s actually missing. I also loosened the “are we still on the right monitor rect?” check — exact pixel match was wrong under DPI scaling and caused false reattach loops.

One night the wallpaper just vanished. Icons on a blank host. No crash dialog. I sat there clicking the tray icon like that would help. Logging eventually showed the cached parent was dead and we were too polite to recreate it. That fix was small. Finding it wasn’t.

If you write Windows wallpaper software: budget more time for Explorer than for your shaders.

Challenge 2: the globe looked fine; the clocks lied

Early on I had collision code that nudged city cards away from each other so labels wouldn’t overlap. Looked tidy in screenshots. On a live map it meant London slowly drifted off London.

I ripped the collision nudge out. Cards stay locked to lat/lon. Overlap happens sometimes. I’d rather have an honest pin than a pretty lie.

Seconds on the clock was another trap. Showing HH:MM:SS made the card width pulse every second unless the layout was locked. Fixed width + optional seconds only for Premium with “show seconds” on. Sounds obvious now. It wasn’t at 2 a.m. when I thought the font was broken.

Weather refresh had a similar “obvious in hindsight” bug. I cleared the weather cache while fetching, the line went empty, the card height collapsed, then jumped back. For a live wallpaper you stare at all day, that blink is loud. Fix: keep the last weather on screen until the new payload arrives.

Challenge 3: themes, monitors, and “it works on my machine”

Once the host was stable, I graded the Natural Earth day map in the fragment shader — sea glass, ember, noir, ink, frost, sand, and the rest. Same textures, different look.

Multi-monitor came next. Listing monitors in Rust was fine. The product question was harder: if someone has three screens, which ones get Orblune? I ended up with per-display enable toggles, and Premium can set a theme per screen. On a single monitor that UI hides itself so the settings page doesn’t look empty and confused.

Dual-monitor testing still surprises me. Sleep one panel, wake it, and Windows rearranges work areas just enough to make you doubt your math.

Challenge 4: shipping with my name on the exe

Publishing scared me more than WorkerW.

Signing: I ship an NSIS installer for the current user (no admin). Without an Authenticode certificate, SmartScreen may warn once. I put that on the site honestly. VirusTotal links go on each GitHub release so people can check the build.

Money: Premium is crypto checkout through a small worker, license signed locally. Getting that path less embarrassing than “email me for a key” took longer than I expected.

I still hit publish. The site is cbybb.github.io/Orblune. If something breaks on your PC, open an issue or mail software.vision@dreambuild.cloud.

What’s next: Mac and Ubuntu

Windows was first because that’s what I use daily, and because the wallpaper hosting problem is very Windows-shaped.

I’m planning native builds for macOS and Ubuntu next. Not a thin Electron wrap-and-pray — I want the same idea (live Earth, clocks, weather) on each platform’s real desktop integration path. macOS and Linux don’t use WorkerW; they have their own rules, permissions, and “please don’t fight the window manager” moments. That’ll be its own pile of notes (probably article 03 or 04 once I have scars to show).

Before that, 02 will stay on Windows: multi-monitor edge cases, updater weirdness, or whatever breaks in my tray logs this week.

口コミ記事を読む前に確認したい5つのポイント

BB — Sat, 22 Aug 2026 08:06:03 +0000

最終確認日は2026年8月22日です。公開情報は変わることがあるので、結論を急がず、公式の案内と照合してください。

なぜ口コミだけで判断すると迷いやすいか

強い見出しや感情的な一文は、読んだ直後の印象を大きく左右します。一方で、その一文がどの事実に基づいているかは、記事の後半や別ページにしか書かれていないことがあります。まずは「何が主張で、何が確認できる事実か」を分けると、読み進めやすくなります。

確認したい5つのポイント

発信者は個人なのか、媒体なのか、公式なのか。 2.いつの情報か。更新日と、事例の発生時期がずれていないか。 3.金額、件数、手順など、検証できる数字や手順があるか。 4.一次情報（公式ヘルプ、契約画面、問い合わせ結果）への参照があるか。 5.同じ主張が、別の独立した情報源でも確認できるか。

事実と感想を分けて読む

「使いにくい」「対応が遅い」といった感想は、その人の状況では正しいことがあります。ただし、それがサービスの全体像と同じとは限りません。感想は感想として残し、契約条件、支払い、本人確認、サポート窓口など、あとから照合できる項目だけをメモしておくと、次の判断が楽になります。

公式情報の当たり方

公式サイトのヘルプ、利用規約、お知らせ、アプリ内の案内を先に開きます。口コミ側の主張と突き合わせるときは、用語が同じか、対象プランが同じか、対象地域が同じかを確認してください。名称が似ていても、別サービスや別時期の話であることはよくあります。

不安が残るときの動き方

お金や個人情報に関わる話なら、口コミのコメント欄で結論を出さない方が安全です。公式の問い合わせ窓口、支払い会社、必要なら公的な相談窓口を使います。スクリーンショットやメール履歴など、自分で残せる記録を先に整理しておくと、説明が短くなります。この記事は、特定のサービスを勧めるためのものではありません。ネット上の評判を読むときの確認手順を、実務的に整理したものです。

DEV Community: BB