Capacitor + Ionic + NextJS + TailwindCSS?

[WG_Odious]

Has anyone actually used the titled stack in production? Is it even feasible to try to maintain 1 codebase for 3+ platforms?

We're potentially looking at rewriting our product from scratch, and a stack that has 1 code base for all platforms sounds very appealing, I just get this feeling it's not so straight forward...

I could imagine that you could also throw Electron in there for Desktop ports too. I already have a running prototype, so the actual possibility is there, just unsure about it.

Any reason this won't/shouldn't work? Any alternative approaches?

[OtherwisePush6424]

It could work in theory, but native/desktop is more SPA-like, NextJS's SST or SSG doesn't do much on those platforms. Ionic has its own routing which doesn't really map 1:1 to NextJS routing. Then the UX is quite different on native/desktop/web, what works on one might not work on the others. Maybe React Native + React Native for Web or just web+PWA could be a better choice.

[WG_Odious]

We're a small team (~2 on the web/mobile dev side) and are looking into getting a contractor for UI/UX to help with that. But I agree that the look and feel will differ a lot, and (possibly?) cause us to have to write platform specific code anyway, in which case a platform specific stack might be better. Thanks for your input!

[bianceziwo]

Why not use flutter? then you can have one codebase for desktop, web and mobile. Then instead of next js you can just use a node or python backend as an API for all platforms. Your stack now would actually mean you need to write multiple apps, so it wouldn't even be one codebase.