docs(android-spike): synthesis — GO, with Stage-1 prototype recommended
All four questions answered: Q1-3 RISKY (credible paths), Q4 PROVEN. WebView- BotGuard POT (YTDLnis-proven) collapses the JS-runtime problem; HLahwani/yt- dlp-android solves Q1+Q2+Q3 together. One open question remains: does WebView- POT recover anti-bot WITHOUT curl_cffi (broken on Android)? The Stage-1 prototype tests exactly that. Fallback: client-to-server app against existing web API. Update ROADMAP 3.2 with pointer to findings. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
dcdf35889e
commit
bd0ebfec1f
2 changed files with 65 additions and 4 deletions
11
ROADMAP.md
11
ROADMAP.md
|
|
@ -172,9 +172,14 @@ alternative that also unlocks signing.
|
|||
|
||||
### 3.2 Android client
|
||||
|
||||
Native client over the existing web API. Background download via
|
||||
WorkManager + JobScheduler. Push notifications via Tailscale-routed
|
||||
HTTPS or a userland push channel.
|
||||
**Feasibility research complete (2026-06).** A standalone on-device engine is
|
||||
credible enough to prototype — see
|
||||
`docs/superpowers/specs/2026-06-27-android-engine-feasibility-findings.md` for the
|
||||
full Q1–Q4 findings and the **go** verdict. Next: a Stage-1 prototype testing
|
||||
WebView-BotGuard POT + HLahwani/yt-dlp-android against real YouTube downloads on
|
||||
a real device, to confirm anti-bot works without curl_cffi (broken on Android).
|
||||
Fallback: a client-to-server app browsing Catacomb's existing web API (the
|
||||
`remote.rs` path).
|
||||
|
||||
### 3.4 Smart auto-tagging — DONE
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue