A phone thatkeeps watch.
I'm building Temivor, an Android assistant for people who run a live app alone. It is built to read your project without changing anything, then tell you what changed, with the source behind every point.
Prototype on demo data
Your project as a landscape. Each red peak is one change in my demo data.
It lives ona phone.
One light, four states
- Watchinga slow breath
- Noticedone sharp pulse
- Needs youa steady red
- All cleardim
Design concept. The light is not built yet.
Temivor is an Android app, built to run on a real phone you can hold, not in a browser tab. The prototype runs in an Android emulator and is installed on my own phone.
Not working yet: the AI model and voice on the phone
Ask whatchanged.
You ask one question. It is built to tell you it is on it, then answer with a short list: what changed, what needs you, and the receipt behind each point. It is read-only by design.
Works today on demo data: the list of changes and their receipts
Not working yet: asking by voice (the prototype starts with a button) and flagging what needs you
- c-001item-001 progress
"50" → "100" - c-002item-001 status
"IN_PROGRESS" → "DONE" - c-003item-002 title
"Review demo" → "Review fixture results"
Real output from the prototype, in an Android emulator, on demo data.
Phone face: concept view, not a real screen. The real output lists the changes but does not yet flag what needs you.
Two ways torun yours.
Today there is one prototype, on demo data. Both ways are future direction.
Yours
On a phone you own, even an old one from a drawer, set on a stand at home.
Future direction. Concept view.
Ours
On a dedicated phone in a stack I would run. One real phone per person, racked like servers, so you keep nothing at home.
Future direction. Concept view, no hosted phones exist.
Concept view. No hosted phones exist yet.
Racked likeservers.
If you would rather not keep a phone at home, yours could live in a rack I would run. Still one real phone, yours alone, with its own light.
Future direction
A real phone also has its own number. One day that could let your assistant send a text or place a call you approve.
Idea only. It must meet carrier terms and telecom rules first, and none of it is built.
Temivor
Said TEM-ih-vor. A working name, not yet cleared.
All clear: when nothing needs you, the light goes dim and Temivor stays out of your way.
Design concept
Where things stand.
As of 18 October 2026
- Works today on demo data
- A prototype Android app takes a request, saves it in a task queue, compares two versions of a demo project and lists what changed, with a receipt for each point. Its core logic passes automated tests on my computer. In an Android emulator the queue kept its tasks through an app restart. The app is also installed on my own phone.
- Not working yet
- The AI model on the phone. Accurate speech recognition. A live connection to a real project.
- Future direction
- Temivor on a phone you keep at home. Temivor on a dedicated phone in a stack I would run. Texts and calls you approve, only once carrier terms and telecom rules allow them. None of these exist yet.
- Not started
- No users, interviews or revenue yet. No price set. Not incorporated.
- Next
- A working AI answer on the phone, then a read-only test on Looseword, my own live app, and interviews with 20 solo developers and student community operators.
One founder.
I'm Andy Li, a third-year computer science student at UBC. I built and run Looseword, a campus community app I launched in October 2026. Temivor is my independent project. UBC is where I study; it does not endorse this venture.
Run a live app on your own?
I'm looking for solo developers and student community operators to talk to about how they check on their projects.
Draft only. Contact is not connected yet.