HXPhotoPicker leaves GIF and web image loading to you, and commits its Pods directory
Imitation WeChat photo/image picker, supporting LivePhoto, GIF image selection, 3D Touch preview, downloading iCloud resources online, editing images/videos, and browsing web images.
At a glance
- What is it?
- HXPhotoPicker is a Swift image and video picker with an editor attached, packaged for both Swift Package Manager and CocoaPods. The design decision that shapes everything else is that it ships no image downloading library of its own, so animated and remote images only work once you plug in an image view.
- Who is it for?
- HXPhotoPicker is worth a look if you are building an iOS app that needs a WeChat style picker with editing attached, and if you want the image pipeline to be your choice rather than the library's. That is exactly what the design gives you: no image downloading dependency, an image view protocol you implement, and separate subspecs so you can take the picker, the editor or the camera alone.
- Can I use it commercially?
- Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 158 days ago.
- What is it written in?
- Mainly Swift, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- SilenceLove/HXPhotoPicker3,424 ★ · +7
| Repository | 2026-09-24 | 2026-11-15 |
|---|---|---|
| SilenceLove/HXPhotoPicker | 3.4k | 3.4k |
7 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
GIF and web images need an image view you supply
The single most useful thing to know about this library is what it refuses to do. It does not bundle an image downloading library, and animated GIFs and remote images therefore do not work out of the box. Instead there is a protocol, named for an image view, that a picker configuration points at. The repository shows three implementations of it in collapsible sections: one built on SwiftyGif, one on SDWebImage and one on Kingfisher at version 6. Each conforms to the protocol, and each shows the same small surface, a method that takes raw image data, a method that starts the animation, and a longer method that takes a download resource with a placeholder, options, a progress handler and a completion handler. Assigning a class to the configuration's image view protocol property is the whole integration.
Web resources cover photo and video, GIF is listed as local only
The feature list separates media types from resource types, and the asymmetry is the interesting part. The supported media types are Photo, GIF, Live Photo and Video. The supported local resource types are the same four: Photo, Video, GIF and Live Photo. The supported network resource types are only two: Photo and Video. So an animated GIF is something the picker can hold when it is already on the device, and not something it will fetch for you, while photos and videos can come from a network resource. The same split shows up in the CocoaPods instructions, where the default pod is annotated as not supporting GIF and web images on iOS 10 and later, and each of the three optional subspecs is described by which library it uses to load GIF and web images.
The package manager and the pod route have different floors
Two installation routes are given, and they are not interchangeable on an older toolchain. Swift Package Manager takes a single dependency entry pointing at the repository with an up-to-next-major constraint from 5.0.5:
dependencies: [
.package(url: "https://github.com/SilenceLove/HXPhotoPicker.git", .upToNextMajor(from: "5.0.5"))
]Underneath that entry there is a warning: Xcode 13.0 or newer is needed for adding resource files and localization files. The requirements section lists iOS 10.0 or newer, Xcode 12.5 or newer and Swift 5.4 or newer, so the package manager route needs a newer Xcode than the stated minimum for its own metadata to work. The CocoaPods route has no such note, and it is the one that carries the subspec granularity. An English version of the documentation exists as a separate file under a Documentation directory, linked from the header, so the Chinese page is the primary one.
Nine subspecs, two of which exclude location
The Podfile block is where the module structure is visible. The default pod is the whole library. Three subspecs each add an image loading library, one per supported implementation. Three more split the library by feature, so you can take only the picker, only the editor, or only the camera, and the camera has its own further split into a full version and a lite version. The lite camera and a separate NoLocation subspec are both described as excluding location, which is the only functionality the camera otherwise pulls in. There is also an Objective-C pod, named for the library with an ObjC suffix, whose comment says it is for versions below v4.0, so it exists for projects that have not migrated. One line in that block is written with backticks around the pod name rather than the usual single quotes, which is a small sign the block is hand maintained.
Permissions are declared per module, not per library
The preparation step is a table of Info.plist keys mapped to the module that needs them, and that mapping is the design. The picker needs the photo library usage description for reading and a second one for adding, and it also reads a key that suppresses the system's automatic limited library alert on iOS 14 and later, with a comment explaining that the picker has adapted to limited access so the user can trigger it deliberately instead. The camera needs the camera and microphone usage descriptions, and nothing else. So an app that embeds only the picker never has to justify microphone access, and an app that embeds only the editor needs neither. That is a real privacy-surface decision, and it is made at the subspec level rather than documented as a caveat.
Four source roots and a committed Pods directory
The repository root has twenty-two entries and they describe the packaging more than the code does. There are four source directories: a general Sources directory, plus Swift, SwiftUI and Objective-C directories alongside it, which is what a library supporting several integration styles looks like on disk. Both distribution manifests are present, a package manifest and a podspec. The example app is committed as a full Xcode project, with a workspace, a project directory and an entitlements file. And then there is a Pods directory and a Podfile.lock, meaning the resolved CocoaPods dependency tree is checked into version control rather than installed on demand. There is also a file called tmp.xcconfig at the root, whose name suggests a temporary build setting file that was never cleaned up. Tooling around it is conventional: a SwiftLint configuration, a coverage configuration, a Travis configuration and a GitHub directory.
The sample code is cut off mid-statement
The quick start snippet shows both calling conventions and then stops. It imports the library, takes a picker configuration whose comment says it matches WeChat's theme, and then shows four async and await forms returning UI images, URLs, asset URL results and asset results, one per line. The last line begins a fifth form using the controller type instead of the static entry point and ends mid-identifier. The retrieval section is similarly partial: an object call that returns a UI image, with a comment noting that for a video this returns the cover image instead, a call that produces an image at a target size and crop mode, and a closure-based call that takes a compression quality. Nothing in these blocks is wrong, but none of them is a complete program, so treat the documentation site rather than the README as the reference.
Editorial conclusion
HXPhotoPicker is worth a look if you are building an iOS app that needs a WeChat style picker with editing attached, and if you want the image pipeline to be your choice rather than the library's. That is exactly what the design gives you: no image downloading dependency, an image view protocol you implement, and separate subspecs so you can take the picker, the editor or the camera alone. Two things to check first. The web image and GIF support is not automatic; it appears only after you assign an implementation, and the repository shows three examples rather than shipping one. And the repository commits its Pods directory along with a lock file and a temporary xcconfig, so read what is checked in before you copy any of its build setup.
Frequently asked questions
How do I add HXPhotoPicker to an iOS project?
Through Swift Package Manager, with a dependency on the repository up to the next major from 5.0.5, which needs Xcode 13 or newer for resource and localization files. Or through CocoaPods, where the default pod can be narrowed with subspecs for SwiftyGif, SDWebImage, Kingfisher, or by taking only the picker, editor or camera.
Does HXPhotoPicker download images from the web?
Web resources are supported for photos and videos, but the image view is yours to provide: an implementation is assigned to the picker's image view protocol property. The repository shows three examples, built on SwiftyGif, SDWebImage and Kingfisher, rather than shipping one.
Which iOS versions does HXPhotoPicker support?
The stated requirements are iOS 10.0 or newer, Xcode 12.5 or newer and Swift 5.4 or newer. The feature list names iOS, iPadOS and Mac Catalyst as the supported platforms, and the README is in Chinese with a separate English file.
Which languages does the HXPhotoPicker interface ship in?
Twelve: Simplified and Traditional Chinese, English, Japanese, Korean, Thai, Indonesian, Vietnamese, Russian, German, French and Arabic, plus an option for a custom language. Further languages are listed as an open item with pull requests invited.
What can the HXPhotoPicker video editor do?
Doodles, stickers including animated ones, text, background music with lyric subtitles, trimming the duration, cropping the size, rotation by any angle, a custom mask, picture adjustments and filters. The image editor covers the same list with mosaic instead of the audio and duration options.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/silencelove-hxphotopicker)Star history chart for your README
[](https://hysenlabs.com/projects/silencelove-hxphotopicker)Was this useful?