How do you develop for multiple platforms in general, should one strive to have multiple frontend folders, one for each platform?

[Axedyson]

I'm wondering what is the best practice way of developing for multiple platforms using only one framework (Tauri)/one codebase. There are features that one needs on mobile but are unnecessary on desktop. An example would be onTouch events on mobile, that I think is not needed on desktop. But that means if you reuse your codebase for all platforms, desktop and mobile will come with unnecessary code that potentially slows the app down? Is this just a tradeoff one has to make if you want to use one codebase or is there some way to handle this? Can tauri remove features that are unnecessary for different platforms when building the final app?

[yajatkaul]

I would personally prefer making mobile apps in something like flutter and desktop apps in tauri for the following reasons

• Different UX needs
• Performance-sensitive apps
• Better platform conventions
• You want true native feel on each platform

Tho ofcoure there can be cases where you might wanna go with tauri only tho thats all up to you.

[Axedyson]

My preference for tauri is that I like the simplicity of one codebase, one tool, which avoids dealing with multiple tools that compromises on the learning curve, maintenance and speed of development

[FabianLars]

In that case it isn't much different than normal web dev where you also have to target mobile and desktop in the same browser.

Since in tauri apps those targets are separate builds though you can use conditional compilation to straight up remove unused code per platform.

On the rust side you can use https://doc.rust-lang.org/reference/conditional-compilation.html and the js side depends on your frontend stack.

[Axedyson]

Cool thanks, I'm using solidjs with vite on the frontend. Is there any way I can conditionally "compile" the solildjs code?

[FabianLars]

with vite i've used https://.com/rollup/plugins/tree/master/packages/replacehttps://.com/rollup/plugins/tree/master/packages/replace together with the env vars tauri sets for beforeBuildCommand https://v2.tauri.app/reference/config/#beforebuildcommand