A5. Find a text-to-speech path that is not the AI Scene
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 66
Description
sendTtsContent pushes text into Rokid's own assistant UI, which the product does not control. Determine whether a custom app can play synthesized speech on the glasses speakers, or whether speech must come from the phone.
Blocks: #spec-notification-grade-permissions (demand grade may speak).
Section A — Hardware verification (needs a Rokid device). Registered from ISSUES.md.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the sendTtsContent path and reviewing the hardware-verification entry in ISSUES.md. Use a registered Rokid device to determine whether a custom app can play synthesized speech through the glasses speakers or whether playback must come from the phone. Done means documenting the verified path and its impact on #spec-notification-grade-permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- embedded-iot, mobile-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100