@ChrisDietric#152461 what would be the biggest benefit for you when bunq would offer a GraphQL API next to the existing REST API? I know there can be benefits, but I am simply wondering what the main benefit for you would be in terms of being able to improve your app. 😀

Indeed, graphql is good but not for everything

@Sander#152487 When you have a good GraphQL API you can reduce a lot a lot of overhead and requests.

@confiq#152530 Sure, but try to setup a Rest API that support more than just a request. For example grouping, sorting, selecting only specific fields.

And I don‘t want to do that on client site, which increases data processing time.

@Christoph-Dietrich-Azure-Hummingbird#152769 I did and it worked fine. Again, it depends what you want from it.
Today standard is and will stay is restapi.

@confiq#152771 I see, there is no need for you personally. No problem.

Just my two cents. 👍👍

There is no need for bunq

@Christoph-Dietrich-Azure-Hummingbird#152768 I agree it can. But building the resolver to resolve these quite complicated queries is not an easy thing. I've not encountered (yet) a situation where I could noticeably speed up my app by selecting only those fields I need. For big scale enterprise applications I know this can make a much bigger impact, but for the average project that connects to the API now I think it might not be worth the investments when comparing to the gains. I think the REST API needs to grow first, in terms of adoption, become more mature (breaking changes from time to time) and then they can look into other forms of APIs. 🙂

@confiq#152773 let me rephrase that; "in your opinion there's no need for bunq." 🙂 other bunqers can still need a GraphQL API.