Hi everyone,
I’ve been working on a lightweight browser utility recently to practice string manipulation and get more familiar with handling real-time browser events.
I built a Morse Code Translator that takes standard text input and maps it to Morse code, and I’m currently trying to refine how it handles rapid inputs.
During development, I noticed that trying to parse every single keystroke instantly for audio playback can sometimes cause slight jankiness or audio clipping on slower devices. I’m currently using a standard dictionary mapping approach for the character conversion.
For those of you who have built similar text-processing or audio-based web tools, I’d love to get your thoughts on a few architectural choices:
-
Input Handling: Do you usually implement a debounce function for real-time text-to-audio parsing, or is it better to queue the events so nothing gets skipped?
-
State Management: Is it overkill to use Web Workers to handle the dictionary lookups and parsing logic for a utility of this size, just to keep the main UI thread perfectly clean?
I’d really appreciate any feedback on the best practices for handling this kind of logic. Thanks!