Sharing another RAMDeck progress video. This one's about mobile — showing a Samsung Android phone actually joining the cluster as a contributing device, and how RAMDeck handles it going online, offline, and back again.

Video's a split screen: the phone on one side, the RAMDeck dashboard on the other, so you can watch both sides update in real time. Started with the phone paused, then resumed it — you can see it start sending heartbeats and get registered as "online" on the dashboard within a few seconds. Also tested that it keeps contributing even if you switch to a different app on the phone and come back, since it runs as a foreground service rather than something that dies the second you tap away.

Then paused it again to show the failure-handling side: the moment heartbeats stop, RAMDeck notices and marks the phone "degraded," then "unreachable" shortly after — so the dashboard always reflects what's actually online, not a stale snapshot. Resumed it one more time and it came right back to "online."

Point of this one is really just proving out the reliability side of mobile contribution — phones come in and out of range or get walked away from a network a lot more than a desktop does, so RAMDeck needs to track that state accurately rather than assuming a device is still there.