I'm working on a PowerApp for photo documentation of construction job sites for various purposes. Currently, images are submitted to a Sharepoint list as "attachments" by the app. Since I was already using Azure SQL as a source for selectable metadata fields (such as selecting the job), I tested out uploading photos to image column which worked, although it was much slower than with Sharepoint as a destination. I'm on the lowest tiered Azure SQL database there is, so that makes sense.
It should be noted that Sharepoint is not the final destination, however I'm only concerened about the performance of taking photos, and being able to be "done" and reliably getting the data to the destination. As the app is currently configured, a Flow runs every time a new row is added to the destination Sharepoint list, which saves each attachment file (.jpg) to that job's on-prem folder on our file server. I'm hoping to work in offline capabilities, with perhaps a default to not uploading unless on wifi which I think is doable.
If anyone has any input on performance levels of various possible destination "data sources" or any other questions/input, I'm all ears.
Side note - I feel as though the term "Data Sources" gives the wrong idea that they are read-only. Perhaps "Data Repository" or something along those lines would make more sense.