Open megsfulton opened 4 years ago
An alternative approach might be to give the user the option to delete the story images/video from their local library after it's uploaded. (Although it might be complicated to message this in a way that's not confusing).
What about when we detect we're running low on storage availability, we show the dialog we already have, and we add another (3rd) option that reads "Clear stories cache" and delete the images produced by the feature?
What about when we detect we're running low on storage availability
Would this be during the error handling flow?
option that reads "Clear stories cache" and delete the images produced by the feature
Would this be retroactive? As in would it go through and delete all images in your device library from WP stories? Or would it be just for the current story and future stories?
Would this be during the error handling flow?
Yes
Would this be retroactive? As in would it go through and delete all images in your device library from WP stories? Or would it be just for the current story and future stories?
This would be retroactive. We could delete all images that have a specific naming convention. So for example if we named the produced files something like wpstory_1234567
we can delete all files that have that prefix name. It would start to fill up again as you continue to create Story slides.
I believe we discussed that it's technically feasible to not save images locally but requires a lot of effort to build.
An alternative approach might be to give the user the option to delete the story images/video from their local library after it's uploaded. (Although it might be complicated to message this in a way that's not confusing).
I'm thinking about devices with low storage limits and how this could quickly add up by creating duplicates in your library if you're mainly using the story creation as a slideshow without adding text or stickers.