Open Juggernaut99 opened 1 year ago
I'm not sure I understand. Do you mean so other apps can send data directly to VN to be spoken without creating a notification, or an option that a user selects to speak a notification that was previously received by VN?
If you can describe how this feature would work in more detail, that will help.
The idea is to listen some notification text by sending request (from bluetooth headset, for example). Use cases:
Do you mean request with a voice command or with a button? I can see either of those being a big challenge to do well, especially if the user can request anything other than the most recent notification, as use cases 1 and 2 appear to imply. I'm not against the idea, but given the difficulty, I don't anticipate getting around to it any time soon.
Use case 3 doesn't quite sound like an explicit request by the user to listen to a notification. There are a few options with related functionality but not quite the same. Queuing notifications to be spoken once the screen turns on or at a set time is a good idea. If that's what it is and not something that happens at the user's request, I would suggest creating another issue for it.
The trigger action (voice command, shortcut or a button) is a matter of choise by user. Triggers can be bind to action by different ways, but they are useless unless you add Intents in your app. As for notification announce, your app is just fine. Anyway, it's up to you to choose what is worth adding.
Perhaps an Android "widget" could be used asr trigger to signal a reread of current notifications. To satisfy this issue, you might have an option for "speak last notification" as well as "speak all notifications" (the feature could be used by request #109 as well.)
Android Widgets might also require accepting intents (I don't know), so handling intents would add flexibility (like control via Tasker, for instance...)
Add an option to announce notification message on user request: by broadcast or activity.