You left your desk and can't remember if you locked your Mac. Lock Status answers that from your iPhone. A free menu-bar helper reports locked, unlocked, or asleep. The iPhone app and its Home and Lock Screen widgets read it back. No account, no servers — status travels through your own private iCloud. Nothing for us to see. What's different: it never fakes confidence. Every reading carries when we last heard from it. Lose contact and it says "Locked · 12m ago", not a reassuring lie.
Maker here.
I built this because I kept walking into meetings unsure whether I'd locked my MacBook, and the only way to find out was to walk back.
Reading lock state turned out to be the easy part. The hard part is that the answer can be stale — the Mac might be asleep, off, or just offline, and a confident "Locked" from data 40 minutes old is worse than no answer at all, because you'd have gone and checked. So every reading carries when we last heard from that Mac, and past three minutes it goes amber and stops claiming to be live. One deliberate exception: a sleeping Mac physically can't send a heartbeat, since its CPU is suspended, so "Asleep" stays confident when it goes quiet.
That principle cost me a feature. I had a "check now" button in the widget, but widgets can't fetch CloudKit reliably inside their execution budget, and it kept reporting "Couldn't reach iCloud" on devices where iCloud was completely fine. Claiming a cause I hadn't established broke the same rule from the other direction, so I cut the button instead of shipping it.
There's no backend. The Mac helper writes to your own private iCloud and the phone reads it back — no account, nothing on my servers, because I don't have any.
The Mac helper is free and the iPhone app is free; Pro adds longer history and insights.
Two things I'd genuinely like feedback on: does the stale/amber treatment read clearly to you, or does it just look like an error state? And what would you want it to tell you that it doesn't yet?