I cannot go into that site because they don't comply with the gdpr right to not allow any legitimate interest cookies with one button, hoping I will click agree instead of going through hundreds of vendors and disabling these illegal trackers

I really appreciate when a dev puts the extra effort in to make a Linux port, but I can understand when a solo dev such as you doesn't have much time to spend on porting. To be honest, I'm just happy if the developers at the very least test the game on Linux using Proton and WINE to make sure it's working well and correctly. That way if making a native port really is that much of a hassle, I expect them to at least test it on Linux. I think that most large teams should make a (good) native port, though.

Native Linux support is always preferable if the developer can handle it or has the budget to do so. However, as long as it works well via Proton, that's the important part. I don't follow him anymore due to several reasons but Gardiner Bryant has a video about this, it's a pretty solid watch: https://www.youtube.com/watch?v=uScsmjvdwyo

Steam Deck and Linux desktop user here.

I wouldn't prioritize a native Linux binary if I were you. For some of my games that have a native Linux version, I still run the Proton compatibility version instead because it runs better. Proton is insanely well-optimized and adapted to Linux desktops, your own code will have a hard time competing with that.

Just make sure to pick an engine / tech stack that works well with Proton and find one or more testers who run SteamOS or another Linux distribution.

Honestly, I wouldn't bother.

Linux is a small market and people who buy exclusively native linux games is even smaller. If your game works fine with Proton that's great.

You're a solo dev and should pick your battles. I would focus on getting steam deck verified instead, if possible.

Honestly, I prefer you go with Proton. Some of the native games I have are quite a few versions behind their windows counterparts. AND most likely it will run better anyways. Better for you, better for gamers. Win-win.

I honestly mostly shop for "SteamDeck verified".

If you yourself use/are familiar with Linux and willing to actually test and polish your Linux version to the same standard as your Windows version, then a native Linux version is always appreciated.

However these days, it's probably not necessary and a lazy afterthought Linux version is like a bad console port, and because we DO have the option to run the Windows version, it's probably worse than no Linux version at all.

So it really depends on your personal feelings towards Linux, and nobody's going to judge you for not providing a native version you can't personally test and support. That's why we have Proton.

I prefer a working Proton build over a untested broken native build. If you can't afford the time to test the Linux builds, go ahead and just rely on Proton.

Testing on Steam Deck so it can be verified probably does make sense from a marketing standpoint though. Mostly checking that controls work, graphic settings are not too demanding by default and font scaling works properly.

Wat? SteamOS is Linux....

Get us some Linux exclusives and we can stick it up towards Windows amirite

I only purchase native titles, because native support means support.

Ideally you should be writing your code to be as portable as possible, in an engine that offers top-notch cross-platform support.

Yes to both. I want games that work well on Linux, so I'm happy with whichever you choose to test. If you provide both, I have options.

Linux native games are great as long as the engine is open source. If it's closed source, it will eventually stop running on up-to-date distros some time after the developer stops updating it. For closed source games, it would be better to develop for excellent wine/proton compatibility so the game will continue to be playable long after it stops getting updates.

Choose whatever is best for you.

That being said, as a Linux user I always appreciate a native Linux version of a game that runs well and is updated promptly.

As far as I know, there are game engines that make it easier to publish on many platforms, but I'm no expert.

Its about practicality.

Even big studios cant handle supporting a native linux version and having it run well while supporting windows versions.. which usually ends up with people running the windows version via proton over the native version (Looking at you, Cities Skylines, Truck Simulator games, and more)

So I would say take the easy route and develop for windows with checks to make sure it runs okay in proton, probably a lot less headache and effort than trying to create a seperate native linux codebase.

Please publish to GoG as well. I want to support sites that are DRM free. Also I think it's smart to give native Linux support to show the industry that Linux is important rather than rely on compatibility tools that may or may not work well for any given game or setup.

I find that native clients are almost always a worse experience than running through Proton. Cursors not hiding or not appearing, inability to adjust certain graphics/display settings, and, rarely, worse performance than through Proton (including not actually managing to init).

That said, Proton has its own irritating quirks. Try turning off mouse acceleration in Skyrim on Linux for instance. Have to use protontricks to find the appid, then you have to nav to it in any of the locations that it could be found (depending on flatpak, native, etc.), and then you have to sift through the prefix to find the bloody INI that has the setting to toggle.

But as an indie dev, you should do whatever makes less work for you so you can do more with your time. If supporting native Linux will increase your workload and detract from work on the game itself, then simply don't support it. Just make sure that your Windows builds work via Proton.

EDIT: Here's a specific example from today. For reference, I normally play everything through Proton so I haven't intentionally loaded a native game for like 6 months. But today I loaded up Yooka-Laylee not realizing it had a native version. Get in, alt tab to screencast on Discord aaand... the game nixed my cursor entirely. I mean, it likely just locked it to the game window, but that still means that I couldn't interact with my PC outside the game window. So quickly downloaded the Proton version and it worked just fine after that.

Sigh... this is exactly the sort of developer decision people were worried about when Proton first came out, and why some Linux users were opposed to it. Obviously in retrospect the benefits of Proton have been worth it, but those folks wouldn't be wrong to say "I told you so."

My take on it is that if you're not developing Xbox-first (which would imply being forced into DirectX etc.) you should pick libraries that give you cross-platform compatibility "for free" (I know it's not that simple, but you know what I mean) to begin with. It has to be part of the plan from the beginning (and integrated into your build/test pipeline, etc.); writing the whole game for Windows first and then trying to add Linux support after the fact is a fool's errand.

At this point, Linux native is almost more like reinventing the wheel. The people working on the compatibility layers have done so much work to make a windows game feel native that you can almost think of them as cross compilers in a weird gross way

Will you only publish it on steam? It would be great to have games available on other platforms like GoG too.