Comment 10 for bug 1643732

Hi Michi, I guess you set the bug status to invalid by mistake?

OK, it looks like I had a very wrong idea of how the storage framework would work. So let me recap my understanding, and please tell me if I got it wrong.

You have your own UI to let the user configure which accounts to use, and to configure what data should be stored there. Applications will not have access to the account information, they will not know to which account the data is being synchronised to and (most important) they won't get any oauth token or other type of credentials, because all the talking with the remote service is done by the storage-framework.

Still, someone needs to add the accounts, and request access to them. When Online Accounts receives a request for a new account to be created, or to grant access to an existing account to a new app, we show the name and icon of that application (see https://wiki.ubuntu.com/OnlineAccounts#App_access ).

We need to sort out what should be shown there. If the application (for instance, the camera app) is not getting direct access to the account, then it seems to me that presenting this request as coming from a "File synchronisation service" is the proper thing to do.

Can you point me at some design documents from the storage framework? Maybe if I saw them I'd understand better how to help you.