[carlotapia]

Some unsolicited feedback:

1) I typed "Hello" and pressed play, and was expecting it to play "Hello". Instead, it played, "The quick brown fox jumps over the lazy dog." What happened? Either the product didn't work as it was supposed to, or there wasn't enough guidance from the UI (i.e., I clicked the wrong play button). I think your app could really benefit from progressive disclosure, which is all about minimizing clutter and focusing the user on fewer, logically connected actions. For example => Type > Play > Export. Here's an article on Medium that covers this, with examples on how companies do it: https://medium.muz.li/design-technique-progressive-disclosur...

2) As a founder that regrets not deeply understanding their market's problem first - What is the problem you solve? Who do you solve it for? Is that problem painful enough and is your solution good enough that someone will pay for it? Are there enough people experiencing this problem to sustain your business? It sounds like you're targeting a very specific audience: Bloggers that do not want to put the effort into podcasting or do not have the ability to podcast, but have enough readership and pent-up demand for a podcast that they would pay to have a text-to-speech tool do it for them. Have you made sure that market exists and is profitable? What are they currently doing to solve this problem?

[billconan]

yes, that play button is confusing to me too. It actually plays a sample of the voice you choose, not what you have typed.

I think the website should provide a sample of what a user has typed.