I have already determined that we want to use Uploadcare in our app to upload images and files (WeWeb is front end - Xano is backend) for many reason - best-in-class uploader, powerful editing tools, etc.
In addition to allowing users to upload files - our app parses and stores attachments from emails, images are used on profiles and in documents that are created and/or collaborated on - and we will ultimately we display tons of avatars while engaged with the platform.
My question is - more from the performance side vs cost - should I consider using Uploadcare for ALL my file, avatar and attachment storage and just manage the Uploadcare token (file UUID) in Xano??
Alternately - I could:
Just use Uploadcare for IMAGES only - (photos & avatars) - storing only Uploadcare token (file UUID) in Xano - and for other files / attachments I could use Xano for the file resource storage.
Just use Uploadcare for uploading / editing - and save the resulting image back to XANO. (performance for previewing / downloading non-image attachments is less important to me vs. avatars & images)
I'd love some thoughts from folks already using XANO + Uploadcare - specifically curious if taking the Uploadcare path for storing all avatars, images would increase performance on the front end. thx!