Cross-platform desktop app filesize comparison

Hello. I am the author of Desktop MP3, an offline music player focused on simplicity and ease-of-use. The MacOS version is built using Objective-C with Storyboard, and the Windows version is built using Delphi with FireMonkey. 

In this article, I want to show the differences between binary file sizes using different cross platform desktop frameworks.

Desktop MP3
Desktop MP3

In a post on X last year, I introduced the Desktop MP3 app, stated my wish to take the codebase cross-platform, and outlined some of the requirements I was looking for in a cross-platform framework. Among other things, one of the main points in that post is that I was looking for a framework that would produce a small binary size.

In the screenshot below you can see binary file sizes of proofs-of-concepts using different frameworks (or versions of those frameworks) that I have tried.

As you might have guessed, Electron resulted in producing the largest binary and the C or C++ based frameworks produce the smaller binaries.

Each framework comes with its own advantages or drawbacks as to what functionality comes included with the framework and what would have to be added. I'm referring to functionality like support for transparent forms, font rendering, UI components, audio playback, multiple windows, etc.

In the following screenshot you can see the proofs-of-concept built using several different frameworks. You'll notice immediately that some made it easier than others to do transparent forms and font rendering.



Side note: while the purpose of this article is to highlight the difference in binary file sizes, it is worth nothing that some frameworks render using immediate mode gui and others render using retained mode gui -- a topic which would be better served by a separate article with a deeper look into CPU and memory usage.

-
Anthony Tietjen is a software engineer with 15+ years experience spanning desktop, mobile and web development. Husband and father, with a passion for music. Connect with Anthony on LinkedIn and X/Twitter.

Comments

Post a Comment

Popular posts from this blog

Parameters Sent by TinyWebDB in App Inventor for Android

TinyWebDB is a component in App Inventor for Android that lets your app communicate with a web page in order to set or retrieve values, rather than storing them on the phone itself. I wanted to know what the TinyWebDB component sends to the web page when it tries to set or retrieve values, so I used Kodingen this morning to write a PHP script that takes the form fields and values sent to the page and writes them to a file. Here is what I found: TinyWebDB.StoreValue sends these parameters: tag value TinyWebDB. GetValue sends this parameter: tag So if you write your own PHP page for TinyWebDB to connect to, you can know if TinyWebDB is trying to store a value if the "value" key exists in the $_POST array. If the "value" key doesn't exist in the $_POST array then you know that TinyWebDB is only trying to retrieve the value for the given tag. As an alternative to using the method outlined by Google , you could use TinyWebDB with your own script written in an...
Read more

Adobe® Flex® Combobox: Selecting an Item Without Using SelectedIndex

In Adobe Flex, in order to select an item in a ComboBox, you use the .selectedIndex property. However, there might be times that you want to specify the item to be selected based on something other than it's position in the list. I have found two potential solutions: ComboBox2 from Ben Forta, Flex evangelist, is a ComboBox component which allows you to specify a "selectedValue" property.   VAComboBox  from Codieron, LTD. (BSD license) Copyright Notice: Adobe, and Flex are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Read more