Migration Guide
What changes when you update SolarLayout, and what to do on first launch of a new version.
When SolarLayout makes a change that touches how you work — sign-in, file formats, the export pipeline, anything user-visible that isn't just a fix or an improvement — we put it here. Each entry walks through the version transition end to end, including anything you might need to do on your end.
If a version isn't listed below, the update is fully behind the scenes: install the new build, launch the app, keep working.
Browser-based sign-in
Sign-in moves from license-key paste to a browser flow on solarlayout.app. The desktop app picks up automatically when you finish — no codes to copy.
The browser already owns identity — passwords, password resets, Google sign-in. Keeping sign-in there means the desktop never touches your credentials directly, and any future identity changes happen in one place.
When future versions ship changes worth a migration note, they'll appear above this line, newest first.