Feature: Text-to-Speech for Viewers

[rahilraipuria]

Text-to-Speech Feature

Overview

The Text-to-Speech (TTS) feature converts written notes into spoken audio.
It enables viewers to listen to notes within the application, improving accessibility for visually impaired users and supporting multitasking.

---

Key Features

• Play/Pause/Stop Controls – Users can control playback seamlessly.
• Multi-Language Support – Read notes aloud in the note’s or user’s preferred language.

---

[rahilraipuria]

@braydenidzenga @MannuVilasara If you find this feature relevant to your project, please assign this to me. Love to work on that.

[MannuVilasara]

Hii @rahilraipuria currently we're onto fixing the small bugs and move to a stable phase, That will take us time of about 2-3 days, this will probably be our next step to implement new features. you can keep the issue here. we'll consider these as our future plans. As of now you can choose anything related to core application that needs to be fixed. I can assign you #59 as the assignee hasn't replied yet if you're willing to work on that.

[MannuVilasara]

I'll assign this and #81 to you but the pr won't be merged so quickly as we're currently migrating to different deployment service

[rahilraipuria]

@braydenidzenga @MannuVilasara Hey, we have two options to do TTS:

1. We can implement Web Speech API, which is a in-browser API, can perform TTS natively on browser and does not require external API call. But the problem with this is, It does not automatically detect the language of page content, may mispronounce, limited language support.

2. Can use a External API (require API KEY) which overcome the about problems but comes with a overhead of API call.

if we dont want heavy support of language, we can go with (1), otherwise (2)

please guide me which one I should proceed with?

[MannuVilasara]

@braydenidzenga @MannuVilasara Hey, we have two options to do TTS:

1. We can implement Web Speech API, which is a in-browser API, can perform TTS natively on browser and does not require external API call. But the problem with this is, It does not automatically detect the language of page content, may mispronounce, limited language support.

2. Can use a External API (require API KEY) which overcome the about problems but comes with a overhead of API call.

if we dont want heavy support of language, we can go with (1), otherwise (2)

please guide me which one I should proceed with?

Thanks for exploring both TTS approaches — that’s really helpful context.
As of now we're working on #96 so I’d prefer we hold off on implementing this feature until the new structure is stable. Otherwise, we might need to rework everything once the redesign lands.
In the meantime, it’d be great if you could:

• design an overall approach how both things will work.
• writing essential files markdown files for the codebase. below is the more information.