TeamAmaze / TeamAmaze/AmazeFileManager
Access from external apps
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
I am trying to use Amaze as default file browser from within my app.
Amaze already listens to the ACTION_GET_CONTENT intent.
It would be amazing to be able to be able to:
- pass a title to the dialog that picks the file instead of having the generic Toast telling to pick a file.
- having a file filter for viewing files by extension (i.e. mimetype)
- be able to pick a folder instead of a file
and maybe not so important, but definitely a cherry on the cake :-) :
- have Amaze show a custom icon for my app's own filetypes
I'm just putting this here supposing that this is the place where to place feature wishes.
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
Start at Amaze's ACTION_GET_CONTENT entry point and trace how external file-picking intents reach the picker dialog. Check how title, MIME filtering, folder selection, and app-specific icons could be represented, then define and test the supported intent behavior for each requested option.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- api, mobile
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100