This content has been marked as final. Show 4 replies
Umm, I think you're pretty much out of luck. If you're using any Flex components, the smallest possible app is going to be over 100K. This has been discussed here before and there's nothing that can be done at this point.
I understand that Flex components can be compileds to not include the Flex framework.
This is beyond my 2.0 experience though.
You understand that the Flex swf is cached in the browser, and that the big hit is in the initial download? Subsequent start-up is much faster.
But yeah, Flex RIAs need broadband, or very committed users.
There is a lot of infrastructure in the Flex Framework (styles, events, layout, effects, etc). These come at a cost in download size, but makes it much faster to write an application than coding this stuff up on your own in Flash. The cost is about 120K for a mini-app. Using RSLs can help if you set it up properly, but the RSL will be 100K or so anyway. If you have a 100K RSL of core components, I would think a mini Menu app wouldn't be another 170K, but I could be wrong about that. However, it might be worth verifying that you got the RSLs setup properly.
Keep in mind that Flex/Flash is a streaming technology. Every Flex app comes with a default preloader (the downloading/initializing progress bar). You can replace that preloader with your own and write a small non-Flex thing that shows something interesting to the user while they stream in the rest of the swf. You could put up a cheap login dialog, ask for user registration, show some billboards, play an animation, whatever. That stuff won't have to run again if the SWF is in the user's browser cache the next time they run the application.