[FEATURE REQUEST] User defined delayed removal of images after auto-upload.
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 4.2k
- Forks
- 3.1k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
The issue with "original file will be: removed from original folder" being immediate means that a new photo can't readily or easily be shared through third party apps because it's no longer local to the phone. Sharing to, for example, Instagram becomes much more difficult if not impossible for less tech savvy users.
Describe the solution you'd like
All images should be backed up immediately, but the removal from the device should be able to be delayed so that photos stay local for some arbitrary period of time to allow for use in other apps. This can be accomplished by a timing setting in the "original file will be" dialogue that lets the user set an arbitrary amount of time before photos are removed from the device. In other apps that sync with servers this is usually accomplished with a field for the user to set a number and a drop down to define the increment of time expressed in hours, days, weeks, months, or years(!?). See mockup below.
Describe alternatives you've considered
I'm not sure there are any.
Additional context
TASKS
- Research (if needed)
- Create branch feature/feature_name
- Development tasks
- Implement whatever
- ...
- Implement unit tests (if needed)
- Code review and apply changes requested
- Design test plan
- QA
- Merge branch feature/feature_name into master
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are mentioned. Start by locating the auto-upload setting and the code that removes original files from the device, then trace how its current timing is configured. Done means users can choose a delay and images remain locally available for that period while backups still occur immediately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100