3

React native versus Google flutter - what would be your two topmost reasons for picking one over the other?

Comments
  • 0
    Flutter, cause dart
  • 0
    @Plasticnova sorry I have never used dart, can you give me a couple major points why dart would be good to use?
  • 1
    1. Performance
    2. I'll choose RN when i need to build an mvp app ASAP. I'll choose Flutter when I got the time to learn dart and it's code patterns.

    So.. yeah🤷
  • 0
    @volttide thank you so much for that..
  • 2
    React Native. More straightforward to use Native code, you get access to the build configuration behind each platform, more open-source modules and components, Sentry support for logging uncaught exceptions, can share Javascript business code between multiple projects and stacks. And if you're daring enough, you can share React Native components with web pages.
  • 0
    📌
  • 1
    https://nevercode.io/blog/...

    A key point in the choice should be the potential of needing community support. React Native is a lot more widely used than flutter and Javascript/Typescript is certainly a lot more widely used than Dart. Unless you are really confident in your dart skills I'd stick with react Native.

    Have you considered and discounted Ionic/cordova?
  • 0
    No! I'm a native Java guy.
  • 0
    @orhun native java = exclusively android?
  • 1
    ask my boy @practiseSafeHex, he raises good points regarding the disadvantages of rn, wanna know what his take on flutter is also.
  • 1
    @AleCx04

    “Horse shit vs cow shit?”

    The answer is: Native
  • 1
    It depends on your requirements:

    Got a team of experienced web devs, then go RN because it's JS so that would be easy.

    But Google being a the driver of Flutter has its advantages too: native interop will probably be better, quicker. Tooling is or will be better.

    Also, RN is from Facebook and Facebook is a criminal company. Google might be too, but they're saints compared to Facebook.

    Still, is go native all the way. Unless Kotlin multiplatform becomes stable and popular some day soon, then I'd go that way.
  • 0
    📌
  • 0
    Thanks everyone for your answers, I am trying to build an app as a side hustle so I was down to trying a new language, but it got me intrigued to understand how people actually choose coz react native and flutter both would serve my purpose and other than the fact that react native has a huge community I cannot put my finger on either of them...at my workplace we use iconic with a native wrapper around coz we had performance issues with Cordova in the past and wanted to write the native side ourself so we have more control but for the side hustle I am still not sure I have figured it out so will keep digging....
  • 0
    @apairathod the fact that your team had performance issues and had to write the native part themselves ... is you answering your own question.

    I realise it’s a different tool. But people believing “this time it will be different” is what gets us into this state. If it’s hybrid/cross-platform you will face these issues. It’s native with many layers of abstraction. Those layers don’t come for free. It will cost you performance, memory, battery and development time learning something completely unique and dealing with bugs that are unique to that platform
  • 0
    @practiseSafeHex hands down native is way way better than any of the scripting languages out there but you cannot ignore the fact that for apps which are not much performance intensive and can get by using node libraries, you save a lot of time and effort making one code base and creating apps for multiple platforms - for me that is one single point that blurs out all the disadvantages of hybrid languages...for the app that I am building , it's for a small business, doesn't need extensive hardware features - it perfectly fits the bill for a hybrid app and I would save time building one code base instead of having the same logic written in android and swift....
Add Comment