Why is there no automatic present?

[MrQinYQ]

If this library has the function of automatic rendering, it will be closer to the development experience in the web environment.
Like the following:

[wcandillon]

On the Web, the browser is responsible for the rendering loop but on React Native we want to let you decide depending if you are using Reanimated or the JS thread for instance. Do you think there is an automatic strategy we could use on React Native? If there is I would love to think about it and implement it if it is compelling. Let me know your thoughts on this.

[MrQinYQ]

My initial idea was to call surface.present on the UI thread at every vsync time, but this didn't seem to work, and my program crashed. This seems to be because react-native doesn't wait for the js thread to finish executing on the UI thread?

Later, I thought of adding an api: requestAnimationFramePost, which will make the callback call after all requestAnimationFrame callbacks are executed. This time I succeeded. But I'm not sure if this is elegant.
Like this:

Do you think this is reasonable? Do I need to submit code?

[wcandillon]

I need to think about it a bit more but I am very interested to understand this better.

…

On Fri, Mar 7, 2025 at 8:47 AM MrQinYQ ***@***.***> wrote: My initial idea was to call surface.present on the UI thread at every vsync time, but this didn't seem to work, and my program crashed. This seems to be because react-native doesn't wait for the js thread to finish executing on the UI thread? image.png (view on web) Later, I thought of adding an api: requestAnimationFramePost, which will make the callback call after all requestAnimationFrame callbacks are executed. This time I succeeded. But I'm not sure if this is elegant. Like this: image.png (view on web) image.png (view on web) Do you think this is reasonable? Do I need to submit code? — Reply to this email directly, view it on GitHub or unsubscribe. You are receiving this email because you commented on the thread. Triage notifications on the go with GitHub Mobile for iOS or Android.

[wcandillon]

This is something we are looking to provide in the near future, let's see if the solution fits :)

[MrQinYQ]

Great, is this work already in development? Which branch is it in?

[fax1ty]

Will be resolved in #357

[wcandillon]

#357 is not the right shape for this I think but yes I think we will get is solved soon.
Now our async model is very clean (and we know where the paths for improvements are) and I think it's a strong foundation to tackle the autopresent.
It's definitely happening.