Our Robot Dog Stole My Phone (And I Built It)

Faraaz Ali Khan — Mon, 26 Oct 2026 17:56:14 +0000

A storage basket, an ESP32, a webcam that knows when you're slacking, and a motor driver that died at 5 AM. The story of Fido, from OxHacks 2026

I put my phone inside the dog and started a focus session.

Then I let my eyes drift away from the screen. Eight seconds, that's all it took. A little white basket on wheels turned towards me. It nudged. I ignored it. It barked. I definitely ignored it.

Then it drove away with my phone still inside it.

That's Fido. Four of us from King's College London built him at OxHacks 2026. He's a robot dog with one job: guard your focus, and if you won't, guard your phone.

Here's how a storage basket from a high-street shop ended up with trust issues ;)

The problem we couldn't stop thinking about

The OxHacks theme was Time.

Everyone's first idea for "Time" is a timer. Pomodoro apps, calendars, to-do lists with AI glued on. We've all downloaded them. We've all ignored them.

Here's the uncomfortable truth we kept landing on: focus tools fail because they live on the device that's distracting you. Screen-time limits are one "Ignore Limit" tap away. You can't out-willpower a phone with the phone.

So what if the consequence was physical? Something you can't swipe away. Something slightly ridiculous. Something with wheels.

What if your phone got taken hostage by a very small, very disappointed dog?

We locked the idea in at 4 PM on Saturday. We had no robot. We had no parts. We had about 15 hours.

How Fido decides you're slacking

You start a 25-minute session in the web app and put your phone on Fido. From then on, Fido has a pair of eyes: a webcam running a focus detector on your laptop.

You…	Fido…
Look at your work	👀 Watches, quietly proud
Look away for 8 s straight	🐾 Nudges you back
Keep going for another 6 s	🔊 Barks
Keep going for another 8 s	🏃 Runs away with your phone
Catch him and tap his collar	📱 Phone back. Session failed. Think about what you did.

Refocus during a nudge or a bark and he calms down. But once he's escaped, there's no bargaining. Running away can't earn you a completed session.

Waiting for your phone → "Hey, eyes over here." → "Fido ran off with your phone."

The eyes 👁️

The detector uses MediaPipe's face landmarker to estimate where your head is pointing. Everyone sits differently, so it doesn't use fixed angles. It spends the first 30 frames of every session learning what "you, focused" looks like, then measures everything against that:

if pitch_diff > c.phone_pitch_delta or (
    pitch_diff > c.phone_pitch_delta_with_eyes_down and s.eye_down > c.eyes_down_threshold
):
    return f"Looking Down at Phone/Lap (ΔPitch: +{pitch_diff:.2f})", True
if pitch_diff < c.look_up_pitch_delta:
    return f"Looking Up / Daydreaming (ΔPitch: {pitch_diff:.2f})", True
if yaw_diff > c.look_away_yaw_delta:
    return f"Looking Away Sideways (ΔYaw: {yaw_diff:.2f})", True
return "Looking at Screen", False

On top of that, Presage's SmartSpectra SDK tells us when you're talking and gives us 478 face landmarks, which we used to catch prolonged eye closure. That's the 4-second micro-nap that hits around 4 AM. Ask us how we know.

Our first version was unbearable. It barked every time you blinked. Two fixes made it feel fair:

Slow to accuse, quick to forgive. You need 8 seconds of sustained distraction before it counts. Look back and the timer drains 3× faster than it filled.
No flip-flopping. "Distracted" kicks in instantly, but "focused again" needs 2 straight seconds of clean readings. No more nudge-watch-nudge-watch strobing.

And because a camera pointed at your face all night is a bit creepy: frames never leave your laptop. The backend only ever sees "YES" or "NO" plus a reason string like "Looking Down at Phone/Lap".

The body: a basket, two wheels, and paranoia

Soon it was raining, then dark, and we were on a supply run to Ryman, Flying Tiger and Tesco, looking at every object and asking "could this be a dog?"

Cardboard, a Ryman bag of possibilities, and biscuits. Biscuits are load-bearing.

The winner was a storage basket. It's the right size, it's rigid, and it's ventilated (so it's basically a chassis). Inside: an ESP32, a dual motor driver, and two geared motors.

A robot built to drive away from people is, by design, a bit dangerous on a crowded hackathon table. So the firmware is paranoid. It asks the backend what to do once a second, and if the answer is late, missing or weird, it stops:

if (WiFi.status() != WL_CONNECTED || millis() - lastReply >= 3000) {
    if (commandFresh) Serial.println("Connection stale -> STOP");
    commandFresh = false;
}

There's also a "Fido can move" switch in the app that works as an emergency stop. Fail closed, always.

And because hackathon Wi-Fi hands out a new IP every time you sneeze, Fido hosts his own Fido-Setup hotspot with a tiny config page. New laptop IP? Connect your phone to the dog, type it in, done. No reflashing.

The trick that let four people build one robot overnight

Two of us were on hardware, two on software, all working at the same time. That only works if nobody is blocked on anybody else.

Our answer was one tiny dictionary:

# Robot hardware acts on this value only, so the hardware
# never needs to know the session rules.
ROBOT_MODES: dict[Phase, str] = {
    Phase.IDLE: "sleep",
    Phase.AWAITING_PHONE: "beckon_dock",
    Phase.FOCUSING: "watch",
    Phase.NUDGE: "nudge",
    Phase.BARKING: "bark",
    Phase.ESCAPED: "run",
    Phase.PAUSED: "rest",
    Phase.COMPLETED: "celebrate",
    Phase.FAILED: "rest",
}

The robot never knows why it's running. It only knows that it should. So at 4 AM, when we decided "Fido shouldn't be able to go straight from running back to watching", the state machine changed and zero lines of firmware did.

Everything else follows one rule: the Flask backend is the single source of truth. The webcam, the robot, your laptop and your phone all read and write one session. The Next.js app streams it live over Server-Sent Events and has no state machine of its own, so two screens can never disagree about how long you have left.

And because the escalation logic runs on an injectable clock, our tests fast-forward time instead of waiting. The whole nudge → bark → escape sequence is tested in milliseconds, and Playwright drives the real journey end to end.

05:00: The motor driver dies

At 4 AM we'd done the grown-up thing: stopped, written every remaining task down, split it into Priority 1/2/3, assigned owners, and drawn up a timeline that ended in "7:00 AM: Completed Product." We felt great.

At 5 AM, the motor driver fried.

No shops open. Plan in tatters. So we swapped in a replacement, re-soldered it, and carried on. It cost us an hour of a perfect schedule, and it taught us this, now written into our firmware notes in capital letters: power the motors separately, never from the microcontroller, and share a ground.

Rewind: how the day actually started

You don't get a robot dog at 5 AM without a 6:37 AM train.

We got to Oxford two hours early, so we did what any responsible hackathon team does: sightseeing.

We all also touched the Thames. For reasons.

The ducks were unimpressed. Fido's first critics.

Then registration, merch, kickoff, and a bubble tea to fuel the 4-hour argument that eventually became Fido.

Oh, and the clocks went back at 2 AM. A hackathon themed Time, on the one night of the year with 25 hours in it. We spent the bonus hour soldering. Obviously.

What we'd tell you before your next hardware hackathon

Agree on a contract between hardware and software in the first hour. For us it was phase → robot mode. It kept four people unblocked all night.
One source of truth. Every "but my screen says…" bug disappears when only one thing owns the state.
Make time injectable. If your logic says "after 8 seconds", your tests shouldn't wait 8 seconds.
Noisy sensors need hysteresis. Turning "on" and turning "off" should have different thresholds.
Robots should fail closed. Stale command = stop. Always.
Bring a spare motor driver. Please. Learn from us.

The humans behind the dog 🐾

Faraaz Ali Khan: Vice President, KCL Tech Society
Dheer Maheshwari: Head of Workshops, KCL Tech Society
Vayun Khare: Co-President, KCL Electronics
Mahraz Ahmed: Co-President, KCL Electronics

Tracks: Time (theme) · Best Handmade Project (Citadel) · Best Use of Presage · Zed · MLH × DEV Writing Challenge · Best use of Delta (Zed Industries)

Code: github.com/itsfaraazak/oxhacks26

So, be honest: how long would you last before Fido ran off with your phone? We're guessing under 25 minutes. 🐶

DEV Community: Faraaz Ali Khan