Thanks for the explanation. I suspect there is no remedy..the key words you provided are
large apps and
lists of screen elements. If you have not already noticed;AI renders the graphical screen very slowly compared to apps built with other platforms. What probably is happening, when the app attempts to initialize, the app attempts to determine what and how the visible objects render on the screen. This activity, in my experience is very slow. Without seeing your code, what you might do is do not provide the update from a list in the Screen1.Initialize (which might be what you are presently doing). Instead, provide a splash screen to display immediately (this could be a Vertical layout set to true and then to false while hiding other screen elements or an actual separate screen; simultaneously use a timer to update the virtual screen from the list. Will this work to improve apparent performance? Perhaps? What would happen is you might be able to provide an image to amuse you or your users while the real app is combing its hair and applying lipstick.
You might try things like that (no you do not actually need any lipstick).
Regards,
Steve