My experience (though I'm not a game developer) is the opposite. Linux users are very demanding, and instead of being thankful that your app works well on Linux, they'll take the fact that it works and works well on Linux for granted, and will resent you for charging money for it.
If you support Ubuntu+Debian (1.15% user base globally on average), the next feature request you'll get will be Xubuntu, Arch, and then some smaller distros which has their own undocumented quirks, they'll ask for 32 bit versions (0.0015%) to run on ancient machines that aren't really powerful enough to run the app anyway, and there goes the rabbit hole.
(In the meanwhile, Windows users are 85%, Mac OS is 13%. We're talking about fractions of fractions a percent here when you move out of Ubuntu x64)
These features will be framed as "You're supporting Ubuntu, getting it to work on this {{similar_distro}} is so close, you should do it and you'll have a lot of users". It's not that they're wrong or malicious — it's just that their concept of a lot of users is a whopping multitude of three people.
I'm also purposefully ignoring the more acrid side of the Linux community where they'll call you names, find your personal email, and make sure it's the first thing you read in the morning for not pulling heroics to make it work for their distro of choice (0.0000075% user base).
All in all, not worth it, really. Not financially, not logically. Not from a human point of view, either.
Here are a few things I've found helpful if you're making a desktop app for Linux:
- Consider charging Linux users for support. This is justifiable because for every Windows support request, there are likely 10 people that experienced the problem and haven't written to you about it, for Mac, 2-3, but for Linux, very likely you're only helping that single guy only. This is the best way to do this, but since my app is free, I don't really want to set up a payment infrastructure.
- Make your app free, and ask Linux users to either make their own builds from unpacked releases, or pay for support for their distro on a rolling basis. You don't really expect anyone to take the latter, but it does wonders to cut down on requests in which people demand you support their favourite obscure distro of choice with no help or support from them.
That said, I still provide Snaps, as it's the closest I can get to a universal Linux runtime. This exposes me to requests to provide AppImage, Flatpak, and some other stuff even then, but it's way better than trying to support distros directly. [0]
[0] I tried to support AppImage, I gave up after a full day of trying. Flatpak had similar issues. One of the core developers of AppImage reached out trying to debug, and I helped him as much as I could — but the point is, while the intentions are pure, and I'm glad for the effort, this is deeper and deeper into the red in terms of price / performance.
I agree that Linux users can also be a pain to deal with :)
But yea from my experience the game market is a little different because there is a growing group of people that rather would not boot Windows for gaming and instead stay on their platform. This group of people is very thankful for ported games.
What I heard third hand from game developers has been that it’s fairly hard to get games to perform well on Linux, and that most of the complaints come because of performance reasons outside the developers’ control.
If you support Ubuntu+Debian (1.15% user base globally on average), the next feature request you'll get will be Xubuntu, Arch, and then some smaller distros which has their own undocumented quirks, they'll ask for 32 bit versions (0.0015%) to run on ancient machines that aren't really powerful enough to run the app anyway, and there goes the rabbit hole.
(In the meanwhile, Windows users are 85%, Mac OS is 13%. We're talking about fractions of fractions a percent here when you move out of Ubuntu x64)
These features will be framed as "You're supporting Ubuntu, getting it to work on this {{similar_distro}} is so close, you should do it and you'll have a lot of users". It's not that they're wrong or malicious — it's just that their concept of a lot of users is a whopping multitude of three people.
I'm also purposefully ignoring the more acrid side of the Linux community where they'll call you names, find your personal email, and make sure it's the first thing you read in the morning for not pulling heroics to make it work for their distro of choice (0.0000075% user base).
All in all, not worth it, really. Not financially, not logically. Not from a human point of view, either.
Here are a few things I've found helpful if you're making a desktop app for Linux:
- Consider charging Linux users for support. This is justifiable because for every Windows support request, there are likely 10 people that experienced the problem and haven't written to you about it, for Mac, 2-3, but for Linux, very likely you're only helping that single guy only. This is the best way to do this, but since my app is free, I don't really want to set up a payment infrastructure.
- Make your app free, and ask Linux users to either make their own builds from unpacked releases, or pay for support for their distro on a rolling basis. You don't really expect anyone to take the latter, but it does wonders to cut down on requests in which people demand you support their favourite obscure distro of choice with no help or support from them.
That said, I still provide Snaps, as it's the closest I can get to a universal Linux runtime. This exposes me to requests to provide AppImage, Flatpak, and some other stuff even then, but it's way better than trying to support distros directly. [0]
[0] I tried to support AppImage, I gave up after a full day of trying. Flatpak had similar issues. One of the core developers of AppImage reached out trying to debug, and I helped him as much as I could — but the point is, while the intentions are pure, and I'm glad for the effort, this is deeper and deeper into the red in terms of price / performance.