04-02-2020, 07:51 AM
(This post was last modified: 08-07-2020, 08:54 AM by jim_chapman.)
Thank you for the suggestion, and for looking into the implementation details. It is certainly something that I would want to keep an eye on. But just now, I think it's the commercial aspect that would be the big problem. If I understand Amazon's pricing model, I would need to pay several dollars, whenever a Freda user got the program to read one book aloud, using a Polly voice. So imagining that, in the course of one month, all my users might between them read a hundred books aloud in Freda, I am facing a cost of several thousand dollars a year.
I can't just swallow that cost, but it would be tricky to find a way to pass it on to the people who are actually using the Polly voices. It would mean adding a new pay-per-use feature to the app, and then trying to balance it so that it did actually recover the right amount of money. Then there is also the work involved in API integration. My past experience of integrating text-to-speech APIs is that even the simple ones take hours to get right, and with Amazon Polly I have the added complication of a dependency on an AWS cloud service. That brings in all sorts of error cases (e.g. any API call might fail because the internet connection is unavailable or interrupted).
That adds up to quite a lot of work, and at the end of the day I am not sure that many people would actually use it, once they realised they had to pay for it (I think that the cost of the feature would come out at around ten cents per hour of reading).
So right now, I am afraid it doesn't look like something I'll be doing soon. But please do feel free to get back to me if you see some solution that I am missing - and thanks, in any case, for your engagement!
I can't just swallow that cost, but it would be tricky to find a way to pass it on to the people who are actually using the Polly voices. It would mean adding a new pay-per-use feature to the app, and then trying to balance it so that it did actually recover the right amount of money. Then there is also the work involved in API integration. My past experience of integrating text-to-speech APIs is that even the simple ones take hours to get right, and with Amazon Polly I have the added complication of a dependency on an AWS cloud service. That brings in all sorts of error cases (e.g. any API call might fail because the internet connection is unavailable or interrupted).
That adds up to quite a lot of work, and at the end of the day I am not sure that many people would actually use it, once they realised they had to pay for it (I think that the cost of the feature would come out at around ten cents per hour of reading).
So right now, I am afraid it doesn't look like something I'll be doing soon. But please do feel free to get back to me if you see some solution that I am missing - and thanks, in any case, for your engagement!