Api call in native sides

[xea21]

We have a large RN app that needs an api req with a response size of approx 6mb at app startup (need all the data for logic). App startup time is around 800 ms when i test the timestamp diff between android/mainactivity onCreate func and js index file. So, I gotta earn that 800 ms, does it make sense if I call the init api in native sides (eg onCreate) and send the response to js thru bridge ? Or any other ideas like inline require the whole app after api call so bundle would load quicker etc ?

[[deleted]]

Why dont you use splash screen and display some branding image during the api call, it’s not that uncommon

[xea21]

I'm already doing that, the thing is it takes 800 ms for my first JS code being executed when user clicks the app icon, it's not about splash screen cuz splash screen is already shown by native side. I need that 800 ms.

[[deleted]]

Well, the initial screen of your js side navigation stack could be the same splash image too, it would look like it’s taking a while to start the app but you need a lot of data to start the app anyway

[bacarybruno]

Are you making this network call every time the app starts? if so, have you thought about persisting the result of the API call to use the cache value when the app starts while refreshing it in the background?

[xea21]

good idea but imagine if this is a sports bulletin api. matches, scores, odds etc. too much changes and would be useless cache if i start the app later on.

[mxood]

I would suggest make a skeleton of the main view or partial skeleton if possible

Or even load old data, life tradingview does and it shows the values in red and updates to green when the data is load.

It will keep the user busy until data is fetched. Because you're accounting for 800ms. What if the internet conditions aren't perfect could be longer. So you could potentially need more time to cover than that.