clipper VS Wails

I've performed a couple experiments remaking Electron apps using Sciter.

My first target was https://github.com/AkashRajpurohit/clipper, a neat little clipboard manager. The owner was gratious enough to officially list my project under the "Clones" section of his readme =D The result was a 6mb file, compared to the original 165mb Electron app.

The second attempt was https://github.com/girkovarpa/temps-lite, an aesthetically-pleasing weather app which was motivated largely by the fact that the original was broken and abandoned yet still had people who wanted to use it. According to the open issues and forks trying to resurrect it, anyway. The file size savings were similar to the former, and they start virtually instantly. The Electron apps have a bit of delay and then a blank window before they finish starting up.

This is basically the same tech stack of an app I’ve been planning to build, but deployed as a desktop application using Wails: https://github.com/wailsapp/wails

Wails 2.6k

The wails project does this when. You can check it out here https://github.com/wailsapp/wails/blob/master/v2/internal/typescriptify/typescriptify.go for inspection.

I have built Web front-ends (React or Svelte) with Go-backend. Embed in a web-view to make it a native desktop app, or get funky and give it native chrome/menus etc. [Wails](https://github.com/wailsapp/wails) is a good candidate to start if you want to cut on boiler plate.

Is that what wails is doing here? (On mobile)

In a "local" environment, where an executable can be provided to someone with the entire game contents. In this case, the game won't use WebSockets, and will instead use a Go/JS bridge (something like Wails) to connect.

Have you seen wails? https://github.com/wailsapp/wails

You should check out https://github.com/wailsapp/wails/pull/1959