Almost still image is a weird way of saying “numerous still images regardless of amount of motion, that have to be stitched together in precise time sorted batches to provide a smooth experience for the viewer.”
Thinking about the use case it’s obvious this isn’t a simple calendar app amount of data.
I bet if you create some images in various resolutions these services support and what looks good to your eye, then fill folders with sequences of them, you’ll see why it’s a lot of bandwidth.
Better to over communicate and let the client deal with the organization as it’s designed to and not let some network admin nickle and dime over bits.
Financial economy doesn’t really say much about the literal economy of building all these toxic gadgets.
Given the big picture, not sure why such a trivial concern as bandwidths ephemeral money cost would foster such strong curiosity.
Thinking about the use case it’s obvious this isn’t a simple calendar app amount of data.
I bet if you create some images in various resolutions these services support and what looks good to your eye, then fill folders with sequences of them, you’ll see why it’s a lot of bandwidth.
Better to over communicate and let the client deal with the organization as it’s designed to and not let some network admin nickle and dime over bits.
Financial economy doesn’t really say much about the literal economy of building all these toxic gadgets.
Given the big picture, not sure why such a trivial concern as bandwidths ephemeral money cost would foster such strong curiosity.
Even then, code is in a repo. Go learn.