Summary
Some Fire TV / ADB failures still surface as messages that are technically correct but not actionable enough for first-time users.
Current behavior
Users may see connection, timeout, or reachability failures without clear guidance on what to verify next.
Expected outcome
Make error states more actionable, especially around:
- ADB not installed / not in PATH
- TV not reachable over the configured IP
- ADB debugging not enabled
- device responded slowly or timed out
Good contribution shape
- tighten existing messages
- map common failure cases to clearer next steps
- preserve the compact desktop-utility tone
Likely files
- crates/core/src/firetv/*
- �pps/tauri/src/features/status.ts
- �pps/tauri/src/pages/*
"@
},
@{
Title='Polish install docs for first-time setup'
Labels=@('good first issue','docs')
Body=@"
Summary
The repo and website already explain setup, but there is still room to make first-run onboarding clearer for contributors and users.
Focus areas
- ADB setup expectations on Windows
- Fire TV debugging prerequisites
- Spotify auth prerequisites
- explicit target device selection
- common first-run failure paths
Expected outcome
Tighten the documentation so a new user can install, connect, and run a first successful action with less guesswork.
Likely files
eadme.md
- CONTRIBUTING.md
- �pps/site/app/install/page.tsx
"@
},
@{
Title='Add tests for binding persistence and favorite ordering'
Labels=@('good first issue','test','backend')
Body=@"
Summary
Bindings and favorite ordering are core to Sendo's reusable workflow model, but they deserve stronger test coverage.
Expected coverage
- save a new binding
- update an existing binding
- delete a binding
- preserve avorite_order
- reorder favorites without corrupting persisted state
Notes
Keep the scope focused on current behavior. This is mainly about protecting existing workflow primitives.
Likely files
- crates/core/src/bindings.rs
- nearby tests or new test modules
Summary
Some Fire TV / ADB failures still surface as messages that are technically correct but not actionable enough for first-time users.
Current behavior
Users may see connection, timeout, or reachability failures without clear guidance on what to verify next.
Expected outcome
Make error states more actionable, especially around:
Good contribution shape
Likely files
"@
},
@{
Title='Polish install docs for first-time setup'
Labels=@('good first issue','docs')
Body=@"
Summary
The repo and website already explain setup, but there is still room to make first-run onboarding clearer for contributors and users.
Focus areas
Expected outcome
Tighten the documentation so a new user can install, connect, and run a first successful action with less guesswork.
Likely files
eadme.md
"@
},
@{
Title='Add tests for binding persistence and favorite ordering'
Labels=@('good first issue','test','backend')
Body=@"
Summary
Bindings and favorite ordering are core to Sendo's reusable workflow model, but they deserve stronger test coverage.
Expected coverage
Notes
Keep the scope focused on current behavior. This is mainly about protecting existing workflow primitives.
Likely files