DAWWW—CORE
DAWWW-CORE/DOCS/access

OFFICIAL GUIDE

Desktop access and account: what is local and what is not

Clearly separate account entitlements, project data, and platform availability.

3 sectionsPractical guide
Project launcher: create, resume, or import a local project.
Project launcher: create, resume, or import a local project.
Screenshots from the current Desktop interface. Exact control placement may evolve without changing the workflow described.
01

1. The account is not the musical source of truth

The account is used for access, entitlements, and some preferences. Working projects remain local-first. Signing in does not automatically turn local projects into cloud projects.

02

2. Desktop is available without a new web payment flow

The public Desktop version does not present a new web payment flow. Existing entitlements remain managed according to their status, while Android follows its separate distribution model.

03

3. Cross-device is based on .dw, not mandatory cloud sync

To move a project between Desktop and Android, the reference mechanism is the portable .dw project. Project compatibility does not depend on permanent server sync.

TIPS

Keep these in mind

  • Export your project before changing devices.
  • Treat the account as an access layer, not a musical backup.
  • For entitlement issues, check the account page; for project issues, check local storage and .dw first.

AVOID

  • Expecting a local project to automatically appear on another device.
  • Confusing Android subscription with project storage.
  • Using account deletion as a way to clear local files.

CONTINUE

Return to the full learning path