Elara

Your proposal seems good. The only problem I foresee is that gzip decompression would have to take place on the watch and I am not sure how expensive that is...

Also, the archive (without compression) could possibly be placed into the already existing DFU zip with a new entry for it in the manifest. That will mean there is still...

> That's a good idea! Assuming it won't confuse companion apps, of course :) It shouldn't, since each file has a name in the manifest, like `bin_file` for the binary...

As long as the name of the asset file always stays the same. The reason I use the manifest is that the names of the .bin and .dat files contain...

I'm wondering how changed assets should be handled. If someone decides to upload a font that is different from the one in the update, how would the companion know not...

No, I mean what if the user wants to modify a resource? Like if an app uses an image of some sort and the user wants to use a custom...

It probably should be handled by companions, but I think it should be standardized, because some users will use Gadgetbridge to update once, and then ITD the next time, and...

Yeah, that's what I was thinking. Maybe a file on the watch that looks like this ``` 764df7d2 a.bin b3e0e55f b.bin ... ``` And then add a characteristic or change...

That works, but we have to consider that it will take up a lot more space

Ok, I have a working implementation of this in my `infinitime` package now. Next step is to integrate that into ITD, which shouldn't be difficult if I do it before...