Although PWAs are useful, standalone apps could even be better for various reasons especially for mobile platforms.
There are two paths to achieve this:
Use a framework like Electron/Tauri/Capacitor. The upside is that the current codebase can be used with slight modifications, the downside is that this, in my opinion, creates an inferior version of the PWA since it's literally the same thing with more overhead and most likely worse performance.
Completely rewrite the project in native platforms. The upside is that the performance would likely increase, and there'd be an actual reason to choose this version over a PWA, downside is that the project would split into (n) different projects each with their own maintenance work.
A positive for both paths, a native app could be distributed through app stores to reach more users. A negative for both paths, they create a lot of development overhead for unknown (possibly negligible) amounts of exposure.
At this point, this issue is more of a suggestion than anything else. It's in 2.0.0 milestone but it's not a promised feature.
Although PWAs are useful, standalone apps could even be better for various reasons especially for mobile platforms.
There are two paths to achieve this:
A positive for both paths, a native app could be distributed through app stores to reach more users. A negative for both paths, they create a lot of development overhead for unknown (possibly negligible) amounts of exposure.
At this point, this issue is more of a suggestion than anything else. It's in 2.0.0 milestone but it's not a promised feature.