Latest release · Website · Support · Release checklist · Changelog · Contributing · Security

Juicr Browse, save, organize, and play.	Home Curated shelves and quick paths.	Discovery Search, browse, and filter.	Library Lists, history, and saved titles.
Details Artwork and playback choices.	Metrics Safe support signals.	Add-ons Optional capabilities users choose to enable.	Login Account access for sync features.

1. Install Juicr. Start with the Android release APK that matches your device, or use the universal APK when you are not sure.
2. Choose your setup. Juicr does not provide media on a fresh install. Enable only the options you want to use.
3. Browse Home and Discovery. Use curated shelves, search, filters, and details pages to find what you want to save or play.
4. Build your Library. Save titles, create lists, revisit continue watching, and keep completed items organized.
5. Open Settings when needed. Tune playback, account, appearance, and privacy-conscious support options from one place.
6. Share safe diagnostics. When support needs evidence, export reports that avoid private source, account, and playback details.

If you like shaping your own setup, Juicr has you covered. Power users can connect personal servers, add trusted add-ons, tune guarded playback paths, and keep separate source lanes organized without turning a fresh install into a one-size-fits-all app.

Diagnostics for these features stay redacted. Juicr uses safe labels, counts, and status signals instead of exposing private server, account, connector, or playback details.

Release assets are grouped by app lane. Android mobile and TV each ship a universal APK plus the same ABI-specific APK set.

flowchart LR
    A["Juicr Android"] --> D["Home and Discovery"]
    B["Juicr TV"] --> D
    C["Juicr Web"] --> D
    D --> E["Library and lists"]
    D --> F["Playback choices"]
    D --> G["Safe diagnostics"]
    E --> H["Account sync when enabled"]
    G --> I["Redacted support evidence"]

Juicr keeps browsing, playback choices, library state, and support evidence separated so users stay in control of what they enable and what they share.

1. Clone the repository.
2. Open Juicr Android/, Juicr TV/, or Juicr Web/ depending on the app lane.
3. Run the narrow setup command for that lane.
4. Use the narrowest lane check available for the code you changed, then confirm CI on the branch.

Use these commands from the matching app folder when building locally:

• flutter pub get to install Flutter dependencies.
• flutter analyze for a focused static check.
• flutter build apk --release for an Android universal release APK.
• flutter build apk --release --split-per-abi for Android ABI APKs.

For release publishing, use the GitHub Actions Android Release workflow. It rebuilds v1.0.1 and future tags from the repository, restores signing from repository secrets, and uploads separated Android and TV APK assets.

• Juicr Android/ - Android mobile app source
• Juicr TV/ - TV app source
• Juicr Web/ - Web/PWA companion source
• assets/ - README and public-safe brand assets
• .github/ - CI, release, Dependabot, and contribution automation
• CHANGELOG.md - release note source
• RELEASES.md - tag and publish checklist
• CONTRIBUTING.md - contribution guidelines
• SECURITY.md - security reporting guidance
• CODEOWNERS - review ownership hints
• LICENSE - repository license terms

Juicr diagnostics are designed to be redacted. Support packets should use safe summaries, screenshots, and timing evidence only.

Diagnostics, logs, app UI, exported reports, and repository examples should avoid private account, source, device, and playback details.

Copyright (c) Team Juicr. All rights reserved.

This repository is available for public viewing only. No permission is granted to copy, modify, redistribute, sublicense, sell, host, or create derivative works from Juicr without written permission from Team Juicr.