TP Watch
Public-signal dashboard experiment.
- scope
- client-side data, public APIs, visual system
- status
- experiment
- stack
- htmljavascriptsvgfinance APIsprediction-market APIs
- tags
- public datadata vizsingle-file
Problem
Public signals are abundant but hard to read together. TP Watch asks what a tiny, opinionated dashboard can do with finance, news, and prediction-market signals when the interface is allowed to have a joke at the center.
The stress indicator is satirical, but the interface question is real: how much can a single-file public-data dashboard communicate without a backend, account system, or heavy charting layer?
What I built
I built TP Watch as one self-contained HTML file. It pulls public finance, news, and prediction-market data client-side and renders a compact TP-CON alert surface.
- One self-contained HTML file with no backend and no build step
- Pulls public finance, prediction-market, and news signals client-side
- Uses a satirical alert layer to make a small data interface memorable
Status
Single-file public-data interface experiment.
Hard constraints make the product decisions better. One file and no backend forced the dashboard to stay focused on signal, hierarchy, and load behavior.