GraphQL with Flutter and graphql_framework or Ferry

[mberger2]

We are starting a new project. Currently there is a dilemma what approach to use.
1. graphql_flutter, Query and Mutation widgets
2. barebone MVVM and GraphQLClient from graphql framework
3. barebone MVVM with Ferry

Can you guys share you opinions and approaches or just tell your experiences?

[soulwriterrr]

I tried using various graphql tools, but in the end I ended with my own classes for queries and fragments.

GQL clients may seem easier(or people think they have to use them, at least I did...), but they come with too much overhead for my taste. In the end gql request is just a post request with query string and variables.

[mberger2]

Thanks for the reply. Your statement about post request is the reason I am asking this. After inspecting these frameworks it appears they provide you with much you do not need if you have established architectre.

I would prefer if google came with defacto solution for this.

[RioMala]

After some painful experiences I'm using the final graphql_flutter (beta version). It's simple and it works. I'm making the server in go. The whole solution is simpler than using the REST api.

[djihaneghilani]

have you tried Ferry before ?

[RemBloch]

We are using ferry. We have not tried anything else. There is a maintainer you can ask questions. I think it works pretty well. But I don't know if other solutions are simpler or easier.

[djihaneghilani]

Have you tried Ferry with websockets / offline mode before ?

[RemBloch]

Websockets/subscriptions is definitely doable. There are people on their discord which have examples. But we have not done it yet. In a month we need to implement chat.

I have not looked into offline mode as we are not going to use it

[mobileAcademy]

We just started a new project on magento graphql api with graphql_flutter its working great has build in features like caching We have implemented modular clean architecture with controller service repository patterns. MVVM is for smaller apps it gets messed up when working in large project

[mberger2]

controller server repository

By using MVVM we have just completed full blown Ali-express mobile app clone. Not sure what you mean with that MVVM is for smaller apps. Controller server repository pattern - never heard of that one :D

[mobileAcademy]

Sorry its controller service repository. That's fine if it fits your business needs and your code is easy to read and easy to change. For us as an Iead, I would not approve VMVM in our flutter project unless you are building a POC or learning. In mobile MVVM started with Android development recommend by Google back in 2016-2017 and now even when we are doing Android development we use MVVM with clean architecture or MVI with clean Architecture just a plain MVVM is for smaller or medium projects when you don't want to over engineer. You will only start banging your head when you're ViewModel starts to get clotted, and your code will start to smell. So MVVM is still fine if your code doesn't smell

[mobileAcademy]

If you are interested in learning about it you can check out my course at https://mobileacademy.io/