The six-platforms-one-codebase part is not usually where these break. The UI layer gets you 90% there and then the last 10% is platform integration, which is per platform by definition.
Two that cost me days on a Tauri 2 app this year: a Mac app launched from the Dock gets launchd's PATH, not your shell's, so anything it spawns cannot find brew-installed tools until you ask the login shell for PATH once and hand it down. And on Windows, merely listing a WSL workspace boots the distro, so the app has to paint from cache and start a distro only on an explicit action.
So my question about "flet build ... prepare it for distribution": how far does that go? Does it handle signing and notarization, or does it stop at producing the bundle? That step is where the cross-platform promise usually ends and you are back to per-platform certificates and per-store review.
joyahmed · · focus · HN ↗
Two that cost me days on a Tauri 2 app this year: a Mac app launched from the Dock gets launchd's PATH, not your shell's, so anything it spawns cannot find brew-installed tools until you ask the login shell for PATH once and hand it down. And on Windows, merely listing a WSL workspace boots the distro, so the app has to paint from cache and start a distro only on an explicit action.
So my question about "flet build ... prepare it for distribution": how far does that go? Does it handle signing and notarization, or does it stop at producing the bundle? That step is where the cross-platform promise usually ends and you are back to per-platform certificates and per-store review.