Would this be an issue when using Journey voice in a large scale mobile-app?

[EPA]

Hello Everyone,

I'm currently finishing a mobile app that leverages the Journey voice (en-US-Journey-F) to read stories. It works really well for my use case, better than all others in the market from what I can tell.

However I have 2 big concerns, it would be awesome if someone from Google or someone experienced could chime in:

• As a consumer app, there will be thousands of users and each user will be creating short stories that become around 3-5 minutes of TTS audio (at most 3 times per day)
• I recently hit an error while testing locally:
  • "data: {"type":"error","content":"8 RESOURCE_EXHAUSTED: Resource has been exhausted (e.g. check quota)."}"
  • This is concerning because I was testing alone, not sure how I could possibly hit a quota, and when I checked the quotas dashboard it shows nothing that would explain this error.
• I also noticed for Journey, it says "preview" - does this mean there is a high likelihood of this going offline at any moment?

TLDR:

• I am concerned that my mobile application will fail once it scales in user count, because of either unavailability of the API for Journey voice (service no longer available), or rate limiting/resource quota.

I am really looking forward to shipping this product with Journey as I believe it elevates the experience. Can someone advise? I am looking to have it in the App stores by Jan 2025.

Thank you! 🙌

[EPA]

Sounds like there is a 30 requests per minute limit on the journey voice -- this is comical. How is this being released by a trillion dollar company? Even 1 user's request sending streamed chunks (let's say 1 or 2 lines at the time) for reading already hits this limit.

This limit completely kills potential for low latency applications of the journey voice 😕