Hacker News Reader

Comment by ghuntley | Hacker News Reader

If this is the experience, no thanks. I stared at a blank screen for about 5 seconds on Firefox mobile before the calculator appeared. Almost gave up.

Note that these are only demos in WASM, one of the targets for UNO. It's mostly a native UI toolkit.

Uno CTO here - We're always chasing performance issues in WebAssembly and I'm curious, are you still seeing the 5 second delay when the app has been loaded once and refreshing? We know that mobile browsers are not particularly efficient with Wasm on mobile devices (particularly iOS), but you may be in a different scenario and/or device.

I'm on a Fairphone 4 using Firefox Mobile. Probably not the most common use case, but it looked like things were failing and I nearly gave up. I'd recommend keeping a few not-cutting-edge CPU devices around and run them with both Chrome and Firefox.

Thanks for the details! We do have lower-end devices to try with, and it's definitely not the best experience. We're currently pinning on the JIT, but troubleshooting is still difficult... much to do in that area.

The native app version of the app generally fares better, even we still have some improvements to make here (the new Android 13 JNI improvements are likely to help us a lot).

Firefox Mobile on a Samsung Galaxy S21 FE 5G with 8GB of ram, I've now been waiting for over 9 minutes for the gallery.platform.uno to load... The bar pretty much stopped moving at about 55% - 60% at minute 2 or so... THis is where I give up.

Edit: I reloaded right after posting the above, and the gallery loaded immediately as a result. Something's wrong with the loader.

iPhone 12 with Safari here, and the app fails to load entirely with a and no further messaging.

I'm on a (wired) multi-gigabit internet connection, and saw some kind of splash screen in Safari. Gave up after 15 seconds while thinking "this has the same qualities as all the other XAML-based platforms".

On a desktop in Chrome, with a fairly powerful processor, its taking ~4 seconds to show the calculator after it makes the call to Uno_UI_Windows_UI_Xaml_Application_Start_Windows_UI_Xaml_ApplicationInitializationCallback.

It takes 5-7 seconds to load in Safari on a M1 Max Macbook Pro, whether on first load or after refreshing. The reason is simple: you have to download all/most of dotnet in wasm form before anything can even begin to run.

I doubt there's anything you can do. It will probably work fine for corporate intranet sites and back office apps with some aggressive caching.

Reply on news.ycombinator.com