In this final chapter, we looked at how to package and distribute Go-based graphical applications. Unlike the distribution of command-line or system utilities, the process of delivering a GUI application requires additional metadata and packaging. Users of graphical apps expect to find and install software in a particular manner that varies based on their operating system. We started by looking at the importance of good metadata and how to select an icon and description that will attract potential users to try out our new software. We then learned how to package assets into our Go-based applications. As the language is designed for single binary distribution, we had to incorporate all supporting files into the executable before distributing. 

Packaging for different platforms can be complicated, so we walked through the steps required to build native-looking graphical packages for macOS, Windows, and Linux. Each package has its own metadata format and package structure but we were able to package our simple application for each of the specific formats. The packages that resulted from this step could be distributed through a website or other file sharing mechanism. However, we wanted to deliver the app where our users would expect to find it—in the system app store. And so we worked through the process of preparing and distributing the packages for each platform's marketplace. The Windows and macOS stores provide an opportunity for applications to earn revenue following release and the Linux software listings will help to increase visibility of our software package.

Having learned the various approaches to building GUIs with Go and exploring the toolkits available, we've made it all of the way to a complete and published graphical application. Hopefully, you've learned a lot along the way and have managed to create the app that you had been aiming to build—using only Go to support a performant, maintainable, and beautiful user interface.