Thanks for signing up and trying it out. We actually drive people to use Descript for most use cases, that aren't relevant. Think Photoshop vs Canva. Since s

Thanks for signing up and trying it out. We actually drive people to use Descript for most use cases, that aren't relevant. Think Photoshop vs Canva. Since speech-to-text APIs have become really good (props to companies like AssemblyAI (https://www.assemblyai.com/ https://www.assemblyai.com/), the transcript-based interfaces are going to become much more common. Our product goal is to solve the use case around making the visual output, when editing/correction isn't the goal. That being said, the editor should be performant and work well, so lots to improve there. As an aside, there are a few evolving open-source libraries that consume the output of these STT services (https://github.com/bbc/react-transcript-editor https://github.com/bbc/react-transcript-editor) and make turnkey transcript interfaces. The newest/most developed one I like is based on Slate, and made by a really amazing engineer at the Wall Street Journal named Pietro. Link: https://github.com/pietrop/slate-transcript-editor https://github.com/pietrop/slate-transcript-editor