A customizable iOS file browser control for browsing, selecting, and deleting local files and directories.
FileExplorer is an iOS library that provides a customizable file browser control for navigating, selecting, and deleting files and directories on the local file system. It solves the problem of integrating native file management features into iOS apps without building a browser from scratch.
iOS developers building apps that require file browsing, document pickers, or file management interfaces, such as productivity, utility, or media applications.
Developers choose FileExplorer for its out-of-the-box support for common file types, extensible API for custom file types, and flexible configuration for selection, deletion, and filtering—all written in Swift for modern iOS development.
FileExplorer is a powerful iOS file browser that allows its users to choose and remove files and/or directories
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows adding custom file types with thumbnails and preview view controllers via the FileSpecificationProvider protocol, as demonstrated in the README's section on adding support for additional file types.
Includes search functionality and configurable filters for file extensions, types, and modification dates, enabling precise control over visible files without extra coding.
Provides immediate support for images, audio, video, and PDF files with native previews, reducing development time for common file types as shown in the GIF examples.
Written in Swift 3.0+, ensuring compatibility with modern iOS development and leveraging Swift's type safety and features for better maintainability.
Limited to browsing and managing files on the local device, with no built-in support for network or cloud-based storage systems, which restricts use in apps requiring remote file access.
Built on UIKit, making it less suitable for projects fully committed to SwiftUI without bridging or additional integration work, as the README does not mention SwiftUI compatibility.
Primary documentation is hosted on CocoaPods and may not be as accessible or up-to-date as embedded docs, potentially slowing down development for those relying on offline resources.