Maybe a REST API Isn't What You Should Use...

Follow for more Android & Kotlin tips 🙌

[koncinar]

It depends whether you can easily request a change (or just do it yourself) of the API or not. If you can, then it's easier to have dedicated REST APIs. But if it's a general use backend, then GraphQL is brilliant.

[jasmeetsingh-or]

A little bit more complicated than the rest api

[ddaypunk]

Work uses this, and it is great to query only for what you want and let the server side handle any additional calls and aggregation.

[NateRidderman]

GraphQL is easier and more powerful for the clients but harder to implement on the backend

[alexnovikov]

GraphQL allows you to use one single request for several connected objects instead of many sequential requests using REST. It could be type safe as well.
Actually, I don't know who is still using REST nowadays 😂

[MrGuppie]

Getting ready to do some GraphQL with AWS Amplify

[amitgupta]

I don't really find Graph QL convenient. For me A regular REST API using Retrofit does the job for me and I find GraphQL a lot more complicated.

[TechBuddy_]

Graphql on the client is fantastic but writing a graphql server kind of sucks

[abbasalidaruwala]

my new company is using GraphQL I am so confused

[litvanika]

GraphQL is fine, but it's quiries are so looong...

[walidaguib]

should i learn backend as a mobile dev

[raouf-kamel]

What do you advise us to use ktor or kobweb..

You have a great shirt
♥

[Narazgul]

Das schreit ja geradezu mal nach einem video mit GraphQL ;)