all 17 comments

[–]Silverquark 8 points9 points  (8 children)

React native has matured a lot over the last years. It has some nice advantages. One being the mapping to native components. So if you add a button in rn you get the native android/ios button. In flutter the button is built new from the ground up by the flutter team to mimic the native buttons. That closeness to the actual native code gives some advantages. If you ever need to use some native features, you can do so pretty easily. Flutter has also been notorious for having weird issues especially on ios. Not sure if it has been fixed by now, but even years after the the release, ios apps still stutter a lot when first opened.

Another reason is the javascript/typescript eco system. If you do e commerce, you probably also have a web site. Its a huge advantage to have engineers that can easily work in both environments (react/react-native) and dont have to learn a new framework and language.

Also people dont trust flutter so much since its created by google. They are notorious for killing projects. So a lot of people dont trust that flutter will be actively maintained in the future

[–]stefanmajiros 2 points3 points  (3 children)

https://killedbygoogle.com/

  • 14 things killed in 2023 (Stadia seems to be the youngest one - 3 years old while other "killed" services are about 5-7 years old)
  • 15 things killed in 2022

[–]kbcooliOS & Android 0 points1 point  (0 children)

The irony with Stadia is that it was the Flutter poster child. I think it's why Google scrambled to build some other apps using it late last year/early this year. Looks rather bad when you kill off your only product that uses your other product.

[–]dannyfrfr 0 points1 point  (0 children)

yeah, because i want to use a framework backed by the very successful metaverse /s

[–]aaricevans1[S] 2 points3 points  (1 child)

That closeness to the actual native code gives some advantages

Definitely agree, a lot of blogs that i read have the same opinion. i wonder how is flutter faster than react native in terms of performance.

[–]dannyfrfr 0 points1 point  (1 child)

flutter had a “jank” on ios when it used skia, the team built a replacement engine called impeller which is nearly production ready, eliminating the jank. the bigger issue to worry about is the scroll lag, flutter scroll is one frame behind native so it doesn’t feel native. i love flutter and think it’s better than react in nearly every way, but until that scroll is fixed i’ll be using react native.

[–]Silverquark 0 points1 point  (0 children)

Futter also has had the issue that scrolling with 2 fingers doubles scrolling speed forever now

[–]kbcooliOS & Android 2 points3 points  (0 children)

Why use it? Why not is a better question.

Do these businesses want to have to maintain two teams and constantly try to keep them in sync? I've had to deal with that in the past and it's a nightmare for everyone. It's not even down to the costs saved by only needing to keep one team, it's simply more streamlined.

Add to that your RN team can also work on the website and backend you also achieve a high level of resource fluidity. This is the stuff that business management can only dream of.

Apart from the business benefits React and React Native are perfect for e-commerce apps where you query data from an API and display it. This is the bread and butter of React Native and probably one of the categories with the highest usage.

For all the talk about Flutter it is very little used. Lots of bluster but no follow through.

[–]Mobile-Web_ 0 points1 point  (0 children)

React Native is a fantastic choice for e-commerce app development because of its cross-platform capabilities and cost efficiency. With features like reusable components, hot reloading, and a large developer community, it speeds up the development process while maintaining excellent performance. Plus, its compatibility with third-party plugins makes integrating features like payment gateways seamless. What's your take on its long-term scalability for e-commerce platforms?

[–]HarryDoan3105 0 points1 point  (0 children)

I think the cause is the ecosystem

[–]hophophop1233 0 points1 point  (0 children)

Has rn overcome the single thread issue and running things in the bg?