Lolly
App openen
  1. Maken
  2. Je werk vinden en bewaren

Sync your devices

Keep your projects, brand and settings the same on your computer, phone and tablet. Lolly copies your work only to one place you choose. You need no Lolly account.

Your storage is the only server involved

The place you choose can be a cloud drive (Dropbox, Google Drive or OneDrive), your own Nextcloud or WebDAV server or your own S3 bucket. The app on each device talks to that storage directly.

A computer and a phone or tablet each sync their local work directly with the shared backup copy in your chosen storage.A computer and a phone or tablet each sync their local work directly with the shared backup copy in your chosen storage.Open this in Diagram Builder

The Privacy page lists every network request the app makes.

From the export panel, you can also send files to the storage you connect for sync and make share links for them. Export a file covers Send to and Links you've shared.

Turn on sync

  • Open Settings → Preferences → Connected services and connect your storage.
  • Under Sync across devices, choose it in Where to sync.
  • Turn on Sync across my devices.
  • On each of your other devices, connect the same storage and do the same. Each device signs in to your storage by itself.

If your storage already holds Lolly data, Lolly asks before it syncs.

In a browser, these buttons and the ones further down say "this browser" instead of "this device".

What syncs

  • saved sessions and projects, including work a tool filed in Projects as you worked;
  • your design systems, with their uploaded fonts and logos, including one added from a Lolly instance such as your organisation's (a locked one stays locked);
  • your uploaded images and the copies of your downloads that Lolly keeps;
  • Convert's file results;
  • your profile and your preferences (theme, layout).

What stays on each device

  • sign-ins, keys and app passwords for your storage;
  • your sync settings and your passphrase;
  • the Lolly instance the app is connected to, and tools installed by a brand pack (a design system you added from a .lolly file does sync);
  • downloaded catalog files and on-device AI models;
  • the revision history of each session.

How sync keeps your work safe

Changes go up by themselves. Lolly uploads a few seconds after you change something, and again when you leave the app. Offline, the change waits until you are back online. The sync section shows when changes are waiting.

Nothing is overwritten by surprise. Before each upload, Lolly checks the copy in your storage. If another device changed that copy and this device has changes of its own, automatic sync stops and asks you to choose.

Another device synced newer work while this device has changes too, so sync stops and asks you. Use the synced copy saves this device first; Keep this device keeps the copy it replaces.Another device synced newer work while this device has changes too, so sync stops and asks you. Use the synced copy saves this device first; Keep this device keeps the copy it replaces.Open this in Diagram Builder

Applying a newer copy can be undone. When another device has synced newer changes, Lolly offers to apply them. Before applying them, Lolly saves this device as Before your last apply. Items deleted on the other device are removed here too, and things you made on this device since it last synced are kept.

You can go back to an earlier copy. Your storage keeps one copy a day for the last seven days, plus the copy from before your last apply. Restore an earlier copy goes back to one of them. Your provider's own version history can keep more. You can also download one of these copies and open the copy in Lolly, or pick the copy in Import data…. The copy is added to the device like a backup. An encrypted copy asks for your passphrase.

Data transfer has the rules for how a copy meets the work already on a device.

Encryption is optional

Turn on encryption when you do not trust the place you sync to.

Waarschuwing: If you lose the passphrase, nobody can open the synced copies

Lolly cannot recover them, so encryption is off by default.

Choose where to sync

What you can use depends on where you run Lolly. In the app, open Settings → Preferences → Connected services → Sync across devices. The list Where this device can sync shows what works on the device you are using, and why the other choices do not.

Which storage works where
StorageBrowser, on lolly.toolsBrowser, on a Lolly you hostDesktop appMobile app
DropboxYesYes, with the site's Dropbox app or your ownYesYes, with the app's Dropbox app or your own
Google DriveYes, with the site's Google app or your own; you sign in once per visitYes, with the site's Google app or your ownYes, when the app includes a Google appYes, when the app includes a Google app; on Android, also needs Google Play services on the phone
OneDriveYes, when the site includes a Microsoft appYes, when the site includes a Microsoft appYes, when the app includes a Microsoft appYes, when the app includes a Microsoft app for phones
Nextcloud or WebDAVNoWhen the site's admin allows your serverYesYes
S3-compatible bucketNoWhen the site's admin allows your bucketYesYes
A file you move yourselfYesYesYesYes

Why the browser on lolly.tools cannot reach your own server: the site lets the page talk only to a fixed list of hosts. That list stops injected code from sending your work somewhere else, and it cannot name every person's own server. The apps allow any secure (https://) address, so they can reach your server directly.

Notitie: Planned, not built yet
  • a folder that another app keeps in step, such as Syncthing or a cloud drive's own app;
  • iCloud Drive in the Apple apps;
  • sync straight to your other device on the same network, with no storage in between.

Set up each kind of storage

Dropbox

Lolly can see only its own app folder in your Dropbox.

Use your own Dropbox app

If the site or app has no Dropbox app of its own, use yours:

  1. In the Dropbox App Console, create an app with Scoped access and App folder access.
  2. Add the redirect URI for where you use Lolly: in a browser, <the Lolly site>/oauth-return.html; in the mobile app, tools.lolly.mobile:/oauth2redirect; in the desktop app, nothing.
  3. In Lolly, paste the app's App key into the Dropbox row and connect.

Google Drive

Lolly can see only the files it created in your Drive.

Use your own Google app

On a Lolly site with no Google app, use your own:

  1. In Google Cloud, create a project and turn on the Google Drive API.
  2. Set the OAuth consent screen to External and add yourself as a test user.
  3. Create an OAuth client of type Web application. Add the site as an authorised JavaScript origin, and <the Lolly site>/oauth-return.html as an authorised redirect URI.
  4. Paste its Client ID into the Google Drive row and connect.

OneDrive

Lolly can see only its own app folder in your OneDrive. Personal accounts and work or school accounts both work.

Nextcloud or WebDAV

  1. In Nextcloud, open Settings → Security and create an app password for Lolly. Do not use your account password.
  2. In Lolly, enter the server address, your user name, the app password and a folder name, then press Save & test.

S3-compatible bucket

  1. Create an access key that can read and write only the bucket and prefix you want Lolly to use.
  2. In Lolly, enter the endpoint, region, bucket, key and an optional prefix, then press Save & test.

A file you move yourself

Open Settings → Preferences → Storage → Move to another device and press Export my data. Move the file to your other device and press Import data… there. This works everywhere and needs no network. Move your work to another device has the steps and what the file holds.

Limits

For people who host Lolly or build the apps

Each provider needs a registration before its sign-in can work. None of these registrations is a server. Each one only tells the provider which return addresses to trust. The sign-in answer comes back to the Lolly site in a browser, to the app itself on the desktop, to tools.lolly.mobile:/oauth2redirect in the mobile app and through Google Play services for Google Drive on Android.

  • Dropbox: one app. Add <site>/oauth-return.html for the web and tools.lolly.mobile:/oauth2redirect for the mobile apps (the desktop apps need nothing). Build values: VITE_DROPBOX_CLIENT_ID, and VITE_DROPBOX_MOBILE=1 once the mobile redirect is added.
  • Google: a Web application client for the site (VITE_GOOGLE_CLIENT_ID), a Desktop app client for the desktop apps (VITE_GOOGLE_DESKTOP_CLIENT_ID and its secret, which Google treats as not confidential for installed apps) and an iOS client for bundle id tools.lolly.mobile (VITE_GOOGLE_IOS_CLIENT_ID). For Android, an Android client for package tools.lolly.mobile with the SHA-1 fingerprint of each signing certificate (debug, release and, if you use it, the Play App Signing key). No client id goes into the build, only VITE_GOOGLE_ANDROID_SIGN_IN=1. The Android sign-in uses Google's Play services library, which is not open source. A build for de-Googled phones or F-Droid sets the Gradle property lollyGooglePlayServices=false, and Google Drive is then unavailable in that build.
  • Microsoft (Entra): one app registration, with the scopes Files.ReadWrite.AppFolder, User.Read and offline_access, open to personal and work or school accounts. Under Single-page application, add <site>/oauth-return.html (VITE_MS_CLIENT_ID). Under Mobile and desktop applications, add http://localhost/oauth-return for the desktop apps (VITE_MS_DESKTOP_CLIENT_ID) and tools.lolly.mobile:/oauth2redirect for the mobile apps (VITE_MS_MOBILE_CLIENT_ID).
  • A self-hosted site must add the download origins used by OneDrive personal accounts to its content policy's connect-src. These can include hosts under *.files.1drv.com and my.microsoftpersonalcontent.com. Set VITE_CONNECTOR_ORIGINS to the exact HTTPS origins your accounts use, rebuild the frontend and deploy the rendered server headers as described in Configure connector origins. Wildcards are not accepted in that setting.