I’d love for something like this to exist (a fast, clean, well-designed mobile and desktop app for backing up my photos with E2E), but I’d only switch from one of the big providers if it were FOSS and I can bring my own backend target (e.g. S3, SMB, FTP).
In a perfect scenario I could generate my own private key to plug into my client devices and just have everything push to private S3 (and then from there archive to the cheapest, coldest glacier tier after it’s been synced to my home storage).
This to me would not be that complicated to build, but would essentially provide E2E Photostream and a backup of last resort in the cloud.
Obviously (as is the problem with all FOSS) you have the dilemma of how do the developers get paid, which I’m sure is why you went down this yet-another-paid-cloud-provider route instead of what I’ve suggested above.
All that said - I like what you’re trying to build, I could see it being useful to some, but providing E2E photo storage as a direct-to-consumer service is IMHO just asking to be held liable later for what your users store there should you gain any considerable traction.
I'm sure this isn't a popular opinion due to the technical know-how involved, but these days I much prefer to selfhost my own services. Far too many times businesses have gone under, changed their practices, had pricing wildly fluctuate, or remove features I wanted. Having setup a handful of useful services on a cluster, I have much more peace of mind involving my data, feature access, etc.
I would love to see a FOSS version of ente available for me to host. My family is currently split amongst multiple photo library services and it'd be nice to say "Here's ours."
In a perfect scenario I could generate my own private key to plug into my client devices and just have everything push to private S3 (and then from there archive to the cheapest, coldest glacier tier after it’s been synced to my home storage).
This to me would not be that complicated to build, but would essentially provide E2E Photostream and a backup of last resort in the cloud.
Obviously (as is the problem with all FOSS) you have the dilemma of how do the developers get paid, which I’m sure is why you went down this yet-another-paid-cloud-provider route instead of what I’ve suggested above.
All that said - I like what you’re trying to build, I could see it being useful to some, but providing E2E photo storage as a direct-to-consumer service is IMHO just asking to be held liable later for what your users store there should you gain any considerable traction.