We're developing a widget that's already over 1.5 MB, and I found it very hard to download the widget successfully (but note there is rare case it indeed succeeds), I wonder what's the limitation of a widget, if there's any? By the way, if possible, I want to download resources, say pictures, first from the network and save them in local storage for later use. But I don't know how to do it with existing API where I only find the recipe one saves a key-value pair, but never a file, permanently.
Local storage of anything but small simple strings is not encouraged and will most likely get rejected by the OEM's. The OEM's use solid state storage which has a discrete amount of write cycles.
What is making your widget so large? The only images that should be included for your widget are navigational and layout images. Anything else should be loaded dynamically via the web.
As I said before, keep in mind that you are working on a device with extremely limited resources, try to load as much content as possible at runtime. Jim
Thanks, Jim. The reason I want to store file locally is that our widget downloads a lot of really big images to display in our full screen view, and we do not want repeat the downloading every time the user gets into the view.
Anyway you help is appreciated. I am going to optimize my code to prevent it form hitting the hardware limitation.