How to Turn a Go GUI App into a Mac App with Parall

[JulyIghor]

I am the developer of Parall, and I have been using it for a very practical workflow on macOS that makes local GUI development much more convenient.

Instead of opening Terminal every time, typing a command, and launching the app manually, I create a lightweight app bundle for the project and pin it to the Dock. Then the loop becomes very simple. Edit code, quit the app, click the Dock icon, and immediately run the latest code from the project folder.

This is especially nice for learning Go GUI development, testing small local tools, and iterating on a project without extra friction.

Here is a simple example using Go and Fyne.

1. Create a Fyne project in a new folder

Create a new folder for the example project:

mkdir ~/Downloads/FyneParallDemo
cd ~/Downloads/FyneParallDemo
go mod init fyneparalldemo
go get fyne.io/fyne/v2@latest

Create main.go:

package main

import (
    "fyne.io/fyne/v2"
    "fyne.io/fyne/v2/app"
    "fyne.io/fyne/v2/container"
    "fyne.io/fyne/v2/widget"
)

func main() {
    a := app.New()
    w := a.NewWindow("Fyne Parall Demo")
    w.Resize(fyne.NewSize(420, 200))

    label := widget.NewLabel("Hello from a local Fyne app")
    button := widget.NewButton("Change text", func() {
        label.SetText("You are running the latest code from your folder")
    })

    w.SetContent(container.NewVBox(
        label,
        button,
    ))

    w.ShowAndRun()
}

Test it once from Terminal:

cd ~/Downloads/FyneParallDemo
go mod tidy
go run .

If the window opens, the project is ready to use with Parall.

2. Run Parall and select Command Shortcut mode

Open Parall and create a new shortcut using Command Shortcut mode.

This is the mode that lets you launch a local command as a normal macOS app, with its own Dock icon and the window created by your Go code. This is not limited to Fyne. It can also work with other Go apps, other GUI frameworks, and more broadly with terminal apps that you want to launch through a normal macOS app shortcut.

3. Enter the command, arguments, and working directory

For this example, use the Go binary as the command.

Command path:

/opt/homebrew/bin/go

Command arguments:

run .

Working directory:

/Users/ighor/Downloads/FyneParallDemo

Environment variables are not needed for this demo, so you can leave that field empty.

4. Configure the shortcut name and icon

Give the shortcut a clean name, for example:

Fyne Parall Demo

Then choose an icon for it. This is a small detail, but it makes the shortcut feel much more like a real app once it is pinned to the Dock.

5. Optionally enable a menu bar icon and Dock icon effects

If you want, enable the menu bar icon for the shortcut.

That gives you another way to identify and access the running shortcut from the macOS menu bar.

You can also enable Dock icon effects.

This is optional, but it adds something that most Mac apps do not have. Instead of trying to mimic a normal app experience, it gives the shortcut a more dynamic and distinctive feel.

6. Export the app bundle, approve it, and use it

Export the shortcut as an app bundle.

macOS may ask you to approve or confirm the app the first time, depending on your system settings. Approve it, then launch it.

After that, you can pin it to the Dock and use it like a normal app.

Why this is useful for learning and testing

This setup is great for local Go GUI development because it shortens the feedback loop.

• You keep your source code in a normal project folder.
• You edit the Go files whenever you want.
• You quit the running app.
• You click the Dock icon again.
• The latest code from the folder runs immediately.

That makes experimentation much easier than going through Terminal every time. It is especially useful when you are learning Fyne, testing UI changes, or building small local desktop tools that you want to relaunch often during development.

This is not about packaging a frozen standalone build for distribution. It is about making local development feel smoother and more natural on macOS.

Parall is available on the Mac App Store and can do much more than this post covers. Learn more here: https://parall.app

[andydotxyz]

I would generally recommend just executing "fyne install" instead. That way you only have to run the compiler once after a change. Just type that in the source code directory and your app will appear alongside all the others.

It's not a bug inconvenience and it is a huge amount more efficient!

[JulyIghor]

This Parall shortcut is not meant to create the final app bundle you would distribute. It is meant to improve the local development loop.

With fyne install, every time you change the code you need to run it again so the installed app gets updated.

With Parall, the shortcut keeps pointing at the project in your folder. So you can just edit the code, quit the app, and launch the same shortcut again from the Dock. No need to run fyne install after every change just to keep the app bundle in sync.

So the value here is not replacing Fyne's packaging flow. It is making local iteration faster and more convenient.