Reducing oakapp download size for incremental updates on OAK-4

mark_xf

Hi Luxonis team,

I'm deploying an OAK-4 app using oakctl app build --publish and noticing that each deployment downloads the full 1.39GB .oakapp package, even when only minor code changes are made between versions.

Current setup:

Base image: luxonis/oakapp-base:1.2.5
App size: ~40MB (DLC model + Python code)
Total download per deploy: 1.39GB

Question: Is there a way to enable incremental/delta updates so that subsequent deployments to the same device only transfer changed layers rather than the full container?

Currently, deploying a one-line code change still requires downloading the entire 1.39GB package, which significantly slows down the development cycle.

Possible solutions I'm wondering about:

Does oakctl support Docker layer caching on the device side?
Is there a way to pre-cache the base image on devices?
Are there plans for delta update support in the oakapp format?
Is there a lighter base image available for apps that only need SNPE inference (no OpenVINO, etc.)?

Thanks for any guidance on optimizing deployment times.

OskarSonc

Hey mark_xf - at the moment, oakctl app build --publish produces a self-contained *.oakapp artifact, and installs from Hub/identifier transfer that artifact as a whole.

For faster iteration, use oakctl app run during development and structure your oakapp.toml so dependencies land in earlier layers and don’t rebuild on every code change.

Thanks,
Oskar