Its modern interface is based on common file selector interfaces like the Windows native - see the demo above.
Cross plattform support
AssetPicker is designed to work with assets from any source - be it cloud storages like Amazon S3, Google Drive or Dropbox or assets from a custom web application server. In opposite to other file managers or pickers, AssetPicker is suitable for hierarchical as well as associative file storages and you can use one or many of them.
Currently adapters for Google Drive, GitHub and EnterMediaDB are available - feel free to ask for the implementation of missing adapters by opening an issue on github
AssetPicker can search recursively loaded hierarchical structures or utilize remote search endpoints. The results will be in one place.
AssetPicker is directly working with the remote storages and thus requires them to support CORS. Anyway some systems don't do that and so the requests need to be proxied - AssetPicker allows to use the included simple PHP-Proxy or any other proxy or another proxy for all or only particular storages.
Actually it's just including the script from a CDN, instanciating the picker with some storages and have buttons with rel="assetpicker" attribute. However there are a lot more options which you can find in the manual