This page answers common questions about the Android app, Google authorization, YouTube source loading, local cache behavior, privacy controls, and the first Google Play release path.
Todij Video Navigator is a native Android app for browsing, searching, sorting, and opening videos from YouTube playlists, liked videos, and subscribed channel uploads.
It is useful when a YouTube account has enough playlists, liked videos, or subscribed channel uploads that searching and sorting locally saves time.
The first Android release focuses on playlists, liked videos, and subscribed channel uploads.
Yes. Once videos are loaded, the app can refine results locally so repeat searches feel faster and do not always require rebuilding the full set.
Yes. The app supports practical sort views such as date, title, channel, duration, views, and likes when that metadata is available.
Yes. The app can open YouTube videos through an in-app player flow and handoff options to YouTube or the browser.
The app is designed for large-library workflows with paging, local cache reuse, retry handling, and capped scans for stability.
The cap protects Android performance, YouTube quota usage, and review stability during the first release. It keeps the workflow predictable for testing.
The first Android release requests youtube.readonly, which allows the app to read approved YouTube account data for the connected user.
No. The Android v1 release is read-only. It does not create playlists, move videos, delete videos, unsubscribe channels, or perform background account changes.
Yes. The Android release path is based on official Google authorization and documented YouTube Data API endpoints.
No. The Android Play release path avoids YouTube watch-page scraping and undocumented endpoints.
No. Todij Video Navigator is a navigation and workflow app. It does not download audiovisual media or provide offline playback of YouTube videos.
Workflow metadata is stored locally on the device to speed up repeat sessions. The app does not operate a TODIJ developer backend/server for user YouTube data in Android v1.
Yes. Settings includes Clear cache and Delete local data controls for app-owned local metadata and workflow state.
Yes. Settings includes Disconnect account so you can disconnect the app locally and clear local authorization state for the app.
No ads or analytics SDKs are enabled in the first Android release.
The current Android release does not include ads, rewarded ads, or cross-promotion ad SDKs.
The Android package name is com.todij.ytnavigator.
The current release line is 1.0.14 with version code 114.
Launch the app, tap Connect YouTube, approve read-only access, open Sources, load playlists or channels, then search and sort results.
Google sign-in can fail if the Play app-signing SHA-1 has not been added to the Android OAuth client in Google Cloud.
For Play App Signing builds, use the app-signing certificate SHA-1 shown in Play Console under App integrity, not only the local debug certificate.
Yes. Internal testing is the recommended first Play track for validating upload signing, OAuth, reviewer instructions, and tester installation flow.
The most common causes are a missing OAuth test user, a wrong Android package name, a missing SHA-1 certificate, or a Google Cloud project mismatch.
The selected source may be empty, private, unavailable to the current account, or temporarily limited by YouTube API response behavior.
Use Clear cache in Settings and reload the source. This rebuilds the app-owned local metadata without changing your YouTube account.
Note the source type, the approximate number of selected videos or channels, the error message shown in the app, and whether Clear cache changed the result.