High usage of Mobile Data

[LeiCraft]

The Passbolt Android App is using up 5 GB of Mobile Data in one Month with a frequent use of the App.
This seams way to high for me

[marc1nm]

Hello, thanks for reaching out. In the mobile app, every time after sign-in (including via autofill), the entire database content is synchronized — this includes resources, folders, tags, users, groups, session keys, and more. Depending on the size and amount of this data, the total transferred payload can become significant, especially when encrypted metadata is used and the app is used frequently, as you mentioned.

At the moment, we don't have benchmark data for network usage, but we'll prepare measurements using a sample dataset to provide a comparison.

[marc1nm]

Hello, I measured networking usage for sign-in + data refresh flow. In the dataset, there are about 600 resources, 5 folders, and 20 users and groups. With this dataset, one sign-in + refresh invocation weighs about 4.5 MB. The size can greatly vary depending on the count, length of the dataset, and size of the fields - ie, in my case, most of the fields are empty, but description can be up to 10k characters.

[LeiCraft]

Thank you for your efforts.
Could we add local encrypted storing of the data for all of the Passbolt clients?
That way we could also acces password when the instance if offline or not reachable.

[marc1nm]

In terms of local storage, all of the above data is stored locally in an encrypted SQL database within the app’s private storage. At the moment, all of the data must be re-fetched to reflect changes made by other users (e.g. sharing, onboarding of new users) or by the same user on other clients (e.g. changes made in the web extension that should appear on Android).

Passwords are the only entity not currently stored offline — they are retrieved from the backend each time they are accessed, by design, for security reasons (although the app is technically prepared to support a local password data source).

To help increase priority for an offline mode for passwords, please submit a feature request here.