🐛 Desktop app doesn't remember maximized state between sessions

[mouadlotfi]

🐛 Desktop app doesn't remember maximized state between sessions

Description

When opening Fladder on desktop, the application does not remember if it was maximized during the previous session. The app correctly saves and restores custom window sizes, but the maximized state is not persisted.

Expected Behavior

• If the app was maximized when closed, it should reopen maximized
• Custom window sizes should be preserved (this already works ✓)

Current Behavior

• Custom window sizes ARE remembered correctly ✓
• When you resize the window to a custom size and close the app, it reopens at that exact size ✓
• However, if you maximize the window and close the app, it reopens in a regular (non-maximized) window with the size it had BEFORE you maximized it
• The maximized state itself is not saved - only the underlying window dimensions

Reproduction Steps

1. Open Fladder
2. Resize the window to a custom size (e.g., 1200x800)
3. Close and reopen → window correctly opens at 1200x800 ✓
4. Now maximize the window
5. Close the application
6. Reopen Fladder
7. Bug: Window opens at 1200x800 (non-maximized) instead of opening maximized

Platform

Windows

App Version

0.10.2

Additional Context

This is a common desktop application feature where window state (maximized vs regular) is persisted to local storage and restored on app startup. The app currently saves window dimensions but not the maximized state flag. Many Flutter desktop apps implement this using packages like window_manager which provides methods to save/restore both window bounds and the maximized state.

Related Issues

• 🐛App exiting fullscreen after playback #452 - Similar issue but specifically about fullscreen state being lost after video playback (fixed for macOS)