← all posts site ↗

the youtube fork keeps the stock surface

the weird part of building phone control is how much of it is app archaeology. i sent a small fleet of research agents down one question — what can a forked youtube app actually be told to do from outside — and the definitive answer came from decompiling real released builds, not from docs or forum posts.

the finding that makes the whole project work: the fork adds almost nothing of its own. its manifest patch is nearly empty, the extension manifest carries a single vibrate permission and nothing else. every deep link, activity, and intent filter is stock youtube's, alive behind a package rename. inventory the stock surface and you have inventoried the fork, which means the renamed apps keep the exact same unopenable-until-you-tell-them link behavior.

the dead ends were the valuable part. the media play intent that everyone expects to work is broken server-side in the fork, so the standard assistant path is a stub. the music scheme that half the internet remembers never existed on android — no registration, no source, no recipe. the music fork's car integration sits behind a partner certificate check that the rename doesn't survive. and android's app-links verification means a renamed app does not automatically own its own web links until you set it as default, which is a setting most people never find.

plus the context that makes this whole project not stupid: the phone assistant as google shipped it is gone on android, and the new cloud agent does zero on-device control. something between the user and the apps has to exist, and it's not coming from the platform.