50 mb limit

[Dave Dyer]

It finally happened, I've hit the 50mb limit on jar size - adding "one more game" to my app,

albeit one with a lot of imagery.   So my jar is now 56 mb, of which 33 mb is images which

I would bet don't affect build times in any material way.

What do you recommend?

[Shai Almog]

This is a bit old but still applicable: https://www.codenameone.com/blog/shrinking-sizes-optimizing.html

33mb is HUGE, it should be pretty easy to reduce the sizes of these images significantly.

[Dave Dyer]

...All good advice for novices, which I am not. Demand for image quality is increasing with increases in pixel density.

I found some default .png splash screens to delete, I vaguely recall including them was an attempt to reduce build
times - which have greatly reduced due to other improvements in the build process.

.. so file this discussion under the long term plans for codenameone. I don't think limiting upload size is a very
effective way of managing resources - your limits on build times are much more relevant.

[Shai Almog]

The 50mb policy isn't likely to change. The server based restrictions aren't enough. They only apply after we wasted a HUGE amount of server resources. This limit applies even to enterprise accounts.

[Dave Dyer]

Hypothetically, if I wanted to embed video or other intrinsically large content in an app, is there a way to

structure it so the limit doesn't apply?

[Shai Almog]

We don't support that use case. You can stream a video via HTTPS pretty easily and also download it dynamically after the app install.

This is MUCH better as it keeps you're app small and allows you to update the video separately. Shipping resources within the app has a lot of drawbacks.