EFFICIENCY IS A PROBLEM

[FaithfulAudio]

Hello All! The title says it all. I've spent the past month migrating our expo app for android and iOS into a non-expo app for react native windows, and it's been dramatic.

Lots of library changes
Moved to RN 79 with new arch enabled
designed exclusively for RN
changed animations like Lottie to frame by frame png for the global loader
currently on V6 of react navigation
Running locally on an M4 Mac with 14 cores and 48gb ram, giving 12 cores to windows and 24-32gb ram to windows.

Release builds are fast enough on my local. However when I submit to the stores, and create the Msix bundle upload of x64, x86, and arm64, and then install on a surface pro 7 with intel i5 and 8gb ram, the difference in handling is dramatic. The app is extremely slow. To the point of being ungodly slow, dramatically slow.

There are some developer warnings I still have in the project that I see natively such as

[UnimplementedProperty] ViewManager = RNSVGSvgView elementClass = RNSVG.SvgView propertyName = vbWidth value = 24

Which repeats for various view managers with vbHeight, vbhWidth, minY, minX

onecoreuap\windows\frameworkudk\warppal.cpp(783)\Microsoft.Internal.WarpPal.dll!00007FFA6C58D094: (caller: 00007FFA6DAA5F14) ReturnHr(37) tid(3844) 80004002 No such interface supported

Out of these two, the unimplemented property repeats quite a lot. I use Lucide React native icons, and react native svg.

Are these dramatically slowing my app down? Drawing a screen seems to take forever. It's not actions on the screen itself once loaded that are really long, but if I save a form for example, it will sit there for like 30 seconds not with the api call (good internet) but I think with the navigation or general processing.

I will be attempting to attack all these debug outputs on the local output, but besides this, am I missing something that makes the app more efficient?

I can't use the Win3 type app creation and have to use the old uwp cpp app because the libraries I want to use don't support the Win3 type app (it seems a lot of libraries are no longer supporting windows updates?)

Please assist all who see this message, especially Microsoft RNW team, I would greatly appreciate your input on making my app more performant.

[austinhallock]

Not a Microsoft team member, but a few things to note:

1. The new architecture has much better performance than the old UWP
2. SVG rendering is very slow - you'll be much better off using a font icon and PNGs instead of SVGs
3. I've never experienced the local build performing better than the release build - on old UWP the release build was always much more performant than local/debug. On new architecture the release build is slightly more performant than local/debug

[austinhallock]

New arch as far as I'm aware is all WinAppSDK not UWP, so not entirely sure what your setup is. If you created on the old arch you'd need to recreate on the new arch rather than just changing experimental props after. Do your main cpp file look something like this? (new/faster) or this? (old/slower)

New is the future and faster, with the drawback being right now everything native you pretty much have to write yourself since react-native libs haven't updated yet.

Generally RNW new architecture is still pretty cutting edge so in my experience there are a decent amount of workarounds I've needed to do. But overall has been solid enough and will keep improving over time :)

If you haven't already, I'd just do process of elimination, commenting out functionality until you figure out what's causing the lag (starting with SVGs and hopefully it's as simple as that).

[FaithfulAudio]

My set up looks like the uwp, so I'm assuming then for new arch, that it's impossible to be new arch unless it's WinAppSDK.

Ok.

I would LOVE to use new arch, here are the libraries that windows is using:

CheckboxWindows (this is a community library)
DateTimePicker (another community library)
ReactNativeAsyncStorage
ReactNativeBlobUtil
ReactNativeFs
RNCNetInfoCPP
RNDeviceInfoCPP
RNScreens
RNSVG (Will remove by re-running everything as non-svg

I'm super open to advice on how to work with these libraries as WinAppSDK.

I am by no means a native windows developer, at best I would try to use Claude AI to recreate some integrations into Win App SDK versions, but even as patches that wouldn't be super maintainable.

I'll keep you posted, if you have any ideas. Or if you're interested in seeing this set up, I'm happy to get some expert eyes on this. tens of thousands of dollars spent already on setting this up, and I need to show something for it.

[austinhallock]

ReactNativeAsyncStorage should work for new arch. Not sure about the rest. But yeah LLMs will be your best friend for this :)

I just have a single native module I've added the functionality I need to, and as community packages get updated I'll swap to them.

If you need help making your own module see #15078 & #15093

[FaithfulAudio]

The SVG to PNG transformation is night and day. The app is much much more performant. I will say that I don't know how I could get away from the libraries that I'm using without a ton more work to be able to upgrade to New arch, which for long term support concerns me a lot, but the immediate viability problem is solved.

[FaithfulAudio]

The SVG transformation to PNG was great. The app is viable now. Thank you Sir!