Does a separate .swc build faster application loading?
SWC is just a compressed zip-like class archive (static library) / Compiling the application with SWC does not change the output of the swf. There are two ways that you can reduce the initial load:
1.RSL is a dynamic library that is loaded separately from the application and can be cached. Any RSL signed by Adobe can be cached not only by the web browser, which is platform-specific caching, but also by the flash player itself, which means that even if the user clears their browser in cache or has no cache at all, once the RSL is loaded, it is cached.
This is usually useful for loading Flex and RPC environments. Another type of RSL caching, as mentioned earlier, is browser caching. In any case, the RSL is loaded at startup.
2. Another way is to extract parts of the application into modules that will be loaded on demand. For example, if an application has 3 screens, each screen is likely to be loaded ["maybe" because the developer has to decide when] when the user first enters that screen.
a source to share
It depends on what makes the startup slow. Is it a slow process after the SWF has been cached by the browser? If that's the case, you just need to structure your code better so that there isn't a lot on startup. You can defer the creation of an object by setting the creationPolicy property on components. If the slowness is due to the size of the SWF, then using RSL frameworks and modularization will reduce the original download size.
a source to share