[radicalriddler]

So I work on a similar project in my spare time, but have just settled for Azure's Text to Speech service.

What I'm actually interested in is your pricing model. Why do you have constraints on characters AND articles, versus just characters? Does doing the conversion cost a static amount that you don't want someone making 10000 requests a month? Or is the article count and hours of audio just an estimation of the 600,000 character limit?

If it's just an estimate of real usage of the actual 600,000 character limit, then I'd try and word it differently, otherwise I feel like I'm going to be heavily constrained by the platform.

[yagudaev]

Yeah great point, I will simplify the pricing and just say "Listen up to 10hrs of audio" instead.

It is a lot more clear and avoids any misunderstandings. Just need to make the changes to the app to do that.

Thanks for the great feedback