@@chhatrapatikumar i don't really move from compose to flutter. i still use flutter in my project. i think its just nice to try out new way to create android app
@@dannndi.youtube yes, FLUTTER beautiful ui , best performance, big community, abundance of resources, tutorials and Libraries are some Pros factors to consider flutter for cross platform solutions.. I liked jetpack compose more than flutter because of kotlin syntaxes, i prefer kotlin syntaxes over dart, well I know both but still kotlin is kotlin!!... Jetpack compose feels easier for me but as you know the lack of a community, resources, tutorials and libraries are some cons factor... Well, flutter is good, as a secondary tool it can be used and also can be used where rapid development is necessary... Jetpack compose seems more clear and structured for me as mvvm clean architecture is really well structured and powerful enough to scale... FLUTTER also can be primary or secondary skill/tool but for me I choose either native Android or iOS as primarily and flutter/react native as secondary... Jetpack compose is really great compared to XML Android, XML is so verbose, unnecessary boilercode, fragments, recyclerview adapter, and can't structure the folders and layout easily like jetpack compose... Hopefully, jetpack compose will rule the native Android and become an industry standard for Android app development in future maybe!!.
good job man 🙌🙌
thanks, appreciate it
this the last part ??
yes, this is the last part
@@dannndi.youtubehey,
I want to ask one thing,why do you move from jetpack to flutter?
@@chhatrapatikumar i don't really move from compose to flutter. i still use flutter in my project. i think its just nice to try out new way to create android app
@@dannndi.youtube yes,
FLUTTER beautiful ui , best performance, big community, abundance of resources, tutorials and Libraries are some Pros factors to consider flutter for cross platform solutions..
I liked jetpack compose more than flutter because of kotlin syntaxes, i prefer kotlin syntaxes over dart, well I know both but still kotlin is kotlin!!...
Jetpack compose feels easier for me but as you know the lack of a community, resources, tutorials and libraries are some cons factor...
Well, flutter is good, as a secondary tool it can be used and also can be used where rapid development is necessary...
Jetpack compose seems more clear and structured for me as mvvm clean architecture is really well structured and powerful enough to scale...
FLUTTER also can be primary or secondary skill/tool but for me I choose either native Android or iOS as primarily and flutter/react native as secondary...
Jetpack compose is really great compared to XML Android, XML is so verbose, unnecessary boilercode, fragments, recyclerview adapter, and can't structure the folders and layout easily like jetpack compose...
Hopefully, jetpack compose will rule the native Android and become an industry standard for Android app development in future maybe!!.