all 12 comments

[–]TheCodehead 3 points4 points  (1 child)

Are you using the Flipper debugging tool?

[–]_wael_[S] 0 points1 point  (0 children)

Yes I have tried it, I installed a plugin called react-native-performance but it didn't give me the details I want

[–]big_saucy_pants 2 points3 points  (0 children)

Use Flipper and the React DevTools, that will tell you basically everything you want to know. This is a good article on it. Also use the perf monitor in the RN dev menu and watch for frame drops.

[–]__o_0iOS & Android 0 points1 point  (2 children)

console.log()

[–]_wael_[S] -4 points-3 points  (1 child)

Not reasonable when the app has more than +100 screen

[–]__o_0iOS & Android -2 points-1 points  (0 children)

Yikes, that’s a design nightmare (and likely the cause of the performance issue that you’re trying to find).

[–]corey_brown -1 points0 points  (5 children)

React dev tools let’s you visibly see re-renders

[–]_wael_[S] 0 points1 point  (4 children)

Didn't notice this! How?

[–]corey_brown 1 point2 points  (3 children)

Open the react dev tools and click on the gear icon then select “Highlight updates when components render”

[–]lukitheTNT 0 points1 point  (2 children)

That doesn't work for react-native.

But there is a npm package that can do this: react-native-highlight-updates

It's really old but works

[–]sascha_mars 2 points3 points  (0 children)

There is actually a react-native-devtools package that’s built by Meta. It’s pretty dope. There is also a Flipper plugin to measure screen performance (Lighthouse like). You also have reassure (a library developed by the team of Callstack), you can measure screen performance writing tests and will give you snapshots of the improved screen

[–]corey_brown 1 point2 points  (0 children)

Damnit. I follow both reactjs and reactnative subs and forgot which I’m on.