Packaging a native graphical application for multiple platforms can introduce additional challenges. A native GUI will typically have to adapt to the current platform and it will need to include package metadata to integrate as expected on a user's desktop. Most graphical apps also require many assets to be embedded into the release package. Additionally, the semantics of installing an application vary from one operating system to another. macOS, for example, expects that applications are packaged as a bundle that can be dragged (or moved) from the Downloads folder into the Applications folder. Windows users will expect a single executable file that will run once downloaded, or an installer that can set up the components required. The platforms you aim to distribute on may impact your application capabilities or the resources it can be packaged with, and we want to do this using a single code base for ease of maintenance.

In recent years, we have seen many platforms create app stores or similar, where users can browse the applications available for their computer. This provides some free marketing and a new channel for downloads, but adds additional overheads for the developer. Screenshots and other metadata about your application will be required as a minimum, and to stand out, you may even need to create a video of your software in action. Stores such as these make installation trivial for the user but often place additional constraints on the developer. Be sure to research these distribution methods if you intend to use them for your application.