3 ms·
The demo and copy are great. Not everyone will agree it is "better" because that's subjective but your website does a good job of telling people it is better an
by harrisonjackson 4y ago
The demo and copy are great. Not everyone will agree it is "better" because that's subjective but your website does a good job of telling people it is better and the demo is good enough that some people will accept what they see/read/hear. :clap:
Your heading makes it seem like you want the direct comparison to AWS polly so maybe add a table to directly compare different aspects of your product vs aws that make it better. Sound quality is just one attribute to compare. What about SDKs, limits, code samples, use cases, more nitty gritty sound comparison details, etc.
Pricing should also be more transparent if you want to compare aws to yours - what maths did you do to get 8x cheaper because at first glance that is misleading.
- jazz3020 4y agoI greatly appreciate the feedback! I agree on the table idea to more candidly and clearly compare other aspects. This launch/experiment was that the quality/cost would be the main factors, and we’d go from there, iterating and customizing it to work for early customers. The 8x math is per 1M characters. I do see that since we’re charging a subscription, it may not be a fair comparison. But the minimum commitment is is so small that I thought it wouldn’t matter for the customers I’m targeting right now. I do think it can be misleading because people might expect pay-as-you-go. We aren’t able to provide pay-as-you-go right now, so I’ll look into updating the copy or how we communicate the subscription model!