It&#x27;s always been slower, but I don&#x27;t think that can be completely fixed since Qt needs to load all of its libraries. Anyway, it&#x27;s still possible to optimize the startup to be very usable.<p>You&#x27;ll want to use a splash screen implemented with minimal UI code (no widgets of any kind yet, just an image with a background). While showing the splash screen, load dynamically a minimal main UI and some critical services -- only the parts that will affect the initial view.<p>Then hide the splash screen. You&#x27;ll have a small bit of time after the UI becomes visible and before the user will actually use it. You&#x27;ll want to use this time to load the rest of your services and preload more UI components to avoid the creation lag on UI thread later on.<p>I&#x27;ve done this kind of three-stage loading on Android without technical users even realizing it&#x27;s not a native app. Would I do it again? Not really if platform native code is an option. There are too many details one has to handle when imitating platform visuals and interaction.