BATON

01iQOO Hackathon 2026 · Chennai Battle

The pocket is the office now.

Your phone captures, thinks on-device, and hands finished work to your desk.

See it thinkOpen the desk
  • on-device
  • 0 bytes to cloud
  • offline-first
  • built for iQOO 15

02The problem

Everything you capture on your phone dies on your phone.

01

Voice notes you never replay.

The idea was clear for ninety seconds in traffic. It has been in the recorder for three weeks.

02

Whiteboard photos rotting in the gallery.

Eleven megapixels of someone else's handwriting, filed between a lunch receipt and a dog.

03

The same thoughts, retyped at a laptop.

The capture took four seconds. Turning it into work takes forty minutes, later, from memory.

Cloud assistants solve the second half of this. They also need a signal, a subscription, and permission to read everything you said.

ACT ICapture

One tap, in the four seconds you actually have.

Hold the volume key and talk. Shoot the whiteboard. Share a screenshot straight into BATON. Nothing to name, nothing to file, nothing to open later.

  • voice · camera · screenshot · text
  • capture works with the screen off
  • stored on device, never uploaded
baton · on-deviceairplane mode
  1. runtimelitert-lm · gemma 3n e2b · int4
  2. inputvoice_note_0947.wav · 47s
  3. steptranscribing…
  4. stepextracting 4 action items
  5. stepdrafting reply · 118 tokens
  6. accelnpu · 11 W-s burst · 2.4 s wall
  7. network0 bytes sent
LiteRT-LMGemma 3n E2BNPU-acceleratedGGUF fallback

ACT IIThink

The model runs on the phone. Not near it.

A Gemma 3n-class model on the LiteRT-LM runtime transcribes, pulls out the action items and drafts the reply — on the NPU, in airplane mode.

The real constraint

On-device AI is limited by heat, not by intelligence — sustained inference throttles a phone within minutes. So BATON never runs sustained. It thinks in short bursts and cools between them. That is exactly what the iQOO 15 is built for: a Snapdragon 8 Elite Gen 5 Hexagon NPU to finish the burst fast, and a 14,000 mm² vapor chamber to absorb it.

ACT IIIHandoff

The work lands before you sit down.

The finished artifact becomes a baton — a small structured packet of summary, actions and draft. It rides the Office Kit flow to the machine you are walking toward.

What it produces is a file and a block of text — exactly what Office Kit's clipboard sync and file drop already carry between an OriginOS 6 phone and the desk.

The route

Phone

  • capture
  • on-device model
  • baton packed

Office Kit

  • clipboard sync
  • file drop
  • screen mirror

Desk

  • baton lands
  • already organised
  • one click from done

designed around the Office Kit workflow · no third-party Office Kit API is claimed or required

04Live demo

Don't take our word. Watch your own browser think.

A small instruct model loads into this page and runs on your GPU. Same shape as the phone build — capture in, structured work out, nothing over the network.

On the phone the same job runs on LiteRT-LM with a Gemma 3n-class model on the NPU. In a browser we use WebLLM over WebGPU, because that is the runtime a browser has — the thesis being demonstrated is the same one: the model is on the device you are holding.

05Against the brief

The five things this is judged on.

01Phone-first execution
The phone is not a remote control for a laptop app — it is where capture, inference and packaging all happen. The desktop only receives.
02AI integration
A local LLM on LiteRT-LM doing transcription, extraction and drafting, NPU-accelerated, with a GGUF/llama.cpp fallback path. Nothing calls a cloud model.
03Office Kit usage
BATON's output is deliberately shaped as a file plus a text block, so it travels on Office Kit's own clipboard sync and file drop. Designed around the flow, not around an API.
04Real-world relevance
Every knowledge worker already captures on a phone and re-types at a desk. This removes the re-typing, and it keeps working in a basement, a flight, or an NDA meeting.
05Final pitch quality
You are reading it. The demo above runs a real model in your browser rather than showing a video of one.

06The desk

Where the batons land.

An inbox of finished work rather than raw material. Every card arrived from a phone with its summary, its actions and its draft already written, and carries the transport it came in on.

baton — desk

07Team

Two people, thirty hours, one relay.

iQOO Hackathon 2026 · City Battle 03
Chennai · 12–13 September

01

Het Patel

Android · on-device ML

LiteRT-LM integration, model packaging, the NPU delegate and the thermal budget that makes bursty inference viable.

02

Utkarsh Rajput

Product · design · handoff

Capture flows, the baton format, the desk UI, and packaging artifacts so they travel the Office Kit flow.