Google Drive/Photos support shipped in Blober. Looking for feedback.

I'm the developer of Blober (blober.io), a desktop app for moving files between cloud providers. Google Drive is supported end to end, and I'm looking for feedback on areas I can make it better.

It moves files between Google Drive and 20+ other providers (Google Photos, Dropbox, OneDrive, pCloud, Box, S3-compatible storage like Backblaze B2 / Wasabi / Cloudflare R2, Azure Blob, Proton Drive, local drives, NAS, etc), in any direction.

Blober can copy a big Drive folder (or your entire Drive, or a "Shared with me" folder) straight to an external drive, NAS, or another provider. Files are transfered in parallel. No Google Takeout, no zip downloads, no waiting for an export to be ready.

You can copy your entire Google Drive to another Google account in one go, and vice versa - Google Docs, Sheets, and Slides come across as .docx / .xlsx / .pptx automatically.

How Blober works:

• Streams Google Drive to a local drive, NAS, or another provider file-by-file. Moving a 1 TB folder doesn't need 1 TB of free space on your machine
• Per-file progress, automatic retry, and resume - an interrupted run keeps the files it already moved.
• It supports path templates such as  media/{file_ext}/{file_created_date}/{filename}. Blober evaluates the template variables to create a destination path.

vs rclone? rclone's Proton backend is Tier 4 experimental, and setup puts your password into a config file. With Blober, you log in through Proton's login page, so your password is never known to Blober.

vs rclone? blober supports some proprietary cloud providers such as GoPro Cloud. With Google Photos, rclone can only download photos it uploaded while blober can transfer all your google photos. With Proton Drive, blober authenticates better and is able to generate thumbnails for images, videos and audio.

I would genuinely like to know whether Blober would solve a problem you personally have.