Ask HN: What are your pain points with current BaaS solutions?

[anasbarg]

I'm building an opinionated domain-specific language for generating GraphQL APIs. You define your schema (models), authorization rules, and you can then extend it's functionality with JavaScript or Python.

I want to know about your pain points with existing BaaS solutions such as Firebase, AWS AppSync/Amplify, etc. so I solve them with the somain-specific language I'm building.

Thank you.

[k0t0n0]

Library support for Zendesk and mailgun. I never feel safe with the default package

[anasbarg]

Let's say that you can use these services while building your backend using a BaaS from the BaaS solution itself natively, would this solve your problem?