ASK HN: Is using GraphQL a good option for building an MVP?

I thought about it quite a bit and in the end, decided it was more of PITA than a benefit. Went with standard REST in the end, and I am still glad we took this decision.

I wouldn't use / introduce it until it became something that is definitely going to add substantial upside (e.g., as part of a backend-for-frontends pattern, or to support some kind of sophisticated query API)

If your main data source is a relational data model, that is tables with relations to each other, I give a strong yes: GraphQL is a very good option. Alternatively consider supabase which provides similar time savers when mainly dealing with relational data.