A bit tricky because, as a hosted free service, I want to keep this free for users and free for me to host. Thus far the DNS name has been the only expensive part (I am terrified of the price when it comes time to renew it).
Perhaps allowing users to specify their own cloud storage solution would be fine - like Google Drive, iCloud or some other cloud storage provider.
Lift data will be stored in an SQLite db in the client so it should be straight forward from a sync perspective, assuming only once device is syncing at any given time (it would break if you edited the same session on two phones).
Given this is SQLite, Turso could be useful as end users could create a Turso account and provide their API key to establish the sync destination.
Cloudflare's D1 wouldn't work as it requires a Cloudflare worker to interface with the database - so end users would need to run a terraform script or something to set up their cloud sync which is probably too many hoops for most people.
I guess I could provide a cloud sync option, but I might need to charge for storage to avoid covering the cost myself - which would require an auth provider (maybe AWS Cognito), subscription management and it starts to blow up in complexity.
A bit tricky because, as a hosted free service, I want to keep this free for users and free for me to host. Thus far the DNS name has been the only expensive part (I am terrified of the price when it comes time to renew it).
Perhaps allowing users to specify their own cloud storage solution would be fine - like Google Drive, iCloud or some other cloud storage provider.
Lift data will be stored in an SQLite db in the client so it should be straight forward from a sync perspective, assuming only once device is syncing at any given time (it would break if you edited the same session on two phones).
Given this is SQLite, Turso could be useful as end users could create a Turso account and provide their API key to establish the sync destination.
Cloudflare's D1 wouldn't work as it requires a Cloudflare worker to interface with the database - so end users would need to run a terraform script or something to set up their cloud sync which is probably too many hoops for most people.
I guess I could provide a cloud sync option, but I might need to charge for storage to avoid covering the cost myself - which would require an auth provider (maybe AWS Cognito), subscription management and it starts to blow up in complexity.