Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 months ago.
Improve this question
I have gone through provider for a basic,
but now want to go deep dive in state management ...so what should I select
PROVIDER, RIVER POD, GETX OR ANY OTHER?
I tried to learn river pod but gone confused as some teaching riverpod, some flutter river pod and some with hook river pod....cant figure out what differences between them...
so suggest me what should I follow....
I am learning for doing a job in future...
Thanks in advance
As I know that provider is the recommended package for state management by google and it depends on MVC design pattern. Still, actually I prefer Bloc over provider because it's the modified version of provider which depends on MVVM design pattern, MVVM design pattern when stands for Model View View Model is the dominant design pattern in android development. Hence, Bloc is more modern than provider but now they both perfect for state management even though many companies out there use provider as well as bloc.
according to your question you don't know what state management the company you're applying for is used so I think you should just understand the concept then you can learn whatever state management out there for work but for now provider is fine.
hope this help
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 days ago.
Improve this question
I am writing a SwiftUI app and am having a hard time understanding the best architectural pattern to go with. I know MVVM is the go-to in mobile development in general, but have also seen sources that say that swiftUI has MVVM built in, so all that is needed is MV. Here is one such source: https://developer.apple.com/forums/thread/699003. This and many other articles say that using swiftUI with MVVM is redundant.
I've also seen other sources that say MVVM is just fine for swiftUI.
Is it just a matter of personal preference? Or, is explicitly defining viewmodels redundant in swiftUI?
Should you factor out the logic that adapts your data model for use by your views? Sometimes.
Do you need a four-letter initialism, a rigid process, or a slew of wannabe-influencers and pundits telling you how to do it? Rarely.
Keep in mind that MVVM was designed specifically for Windows Presentation Framework. If you're looking for an app architecture designed for SwiftUI, try the Composable Architecture.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I was reading on the net and I was training a little. I am developing an app with Xamarin but too many problems, endless crashes and very slow builds. Looking for alternatives, I came across Flutter, which has a good reputation (I don't know, I've ever used Flutter) compared to what aspects is one better than the other? And is there any way to import a Xamarin.ios project to flutter?
It depends on your requirements and your skill set. If you have experience in .Net development and you have knowledge of c# you can go with Xamarin. You will find it more similar.
But if you are beginner and your aim is to learn new technologies then defiantly you should go with Flutter and dart. As it have better performance and Hot Loading features which are not that good in Xamarin.
Also xamarin is coming with new updates you must be aware of it, i.e. .Net MAUI the extended version of xamarin forms. So in that also you have to learn new things and adopt it.
There is not way to directly import your Xamarin.iOS project into
Flutter as of now, you have to migrate it manually.
For more information you can read some articles which are available on simple google search, here are some useful links:
https://blog.codemagic.io/flutter-vs-xamarin-a-developer-s-perspective/
https://blog.logrocket.com/xamarin-vs-flutter/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I started build an e-commerce app that allows people buy one item by turn. However, I don't have deep knowledge about Flutter app architecture to follow. The app will get all data from a server and will persist only basic user data in the mobile device. I want to know which are the patterns and architectures (state-management) to study and apply considering that I am a beginner in Flutter.
I think that your question is pretty subjective as it could have as many answers as State management libraries+architectures exist in flutter.
But I would step up and recommend something like shown here.
The architecture uses Provider + ChangeNotifier which is recommended by google, and to me personally is both a simple and powerful approach.
You might be advised to use Bloc , which is indeed good too and also recommended by google here but in my opinion more complex for beginners. And there is nothing you can you do with Bloc that you can't achieve with provider.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 days ago.
Improve this question
I am a beginner in Flutter. I want to make a Food delivery app, I have seen many state management types such as Provider, bloc, getx, and redux. Actually, I am so confused, which one to use. I think there are more confused like this. I have read provider is google recommended but still, they use bloc. So I have started learning but I have seen many complex apps uses bloc. So is there anyone please suggest to me, which one I want to use?
I have used bloc (with rxdart), mobx, provider to varying degrees.
First of all, the provider is officially recommended. There is nothing wrong with using it. I have used the provider myself.
I recently learned about getx. I looked at the documentation and found that the functions are very rich and not redundant. It can be independent. I think it can be tried and used. If you don’t have a favorite, you can take a look at getx. It will let you Development is more convenient
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 5 years ago.
Improve this question
I am studying the current architecture of uber rider app and I got to know the current rider app was evolved from MVC to a specific architecture called riblet, which is designed on top of viper by Uber themselves. As I understood riblets is independently testable pieces that each have a single purpose. I'm aware that the new architecture is capable of handling performance and scalability. I am interested in knowing the cons of riblet architecture.
Okey. I found some cons of the riblet architecture. I will post them here to discuss with anyone who is interested. The main cons are as follows,
Since there is a higher number of independent riblets communicating through their interfaces, there is a probability of failure of a particular interface compared to a system with fewer components.
Yes testing a single riblet is easy yet it makes integrations and handling the requests among riblets more complicated.
Changing the technology stack in the long run is difficult