Your server or somebody else should never ever have access to the unencrypted seed, if not needed.
You could connect your app with a centralized server and store a securely encrypted seed-file there.
- User visits your website / app
- User sees "Connect with Dropbox / Google Drive"
- User Login with OAuth @ Dropbox / Google Drive
- User sets a secure password at your application
- Generate a new seed (cryptographically secure)
- Encrypt the seed with the password (see key derivation functions / AES)
- Encrypted seed is stored at Dropbox / Google Drive
When you want to store the securely encrypted seed on your own server, you could use Secure Remote Password protocol (SRP) for the authentication. This way you could use the same password for authentication and encryption.