Hi HN,
I originally switched from PyQt5 to Tauri to get smaller desktop binaries and better performance. Later, I wanted to add a web version and put everything into a monorepo.
That's when I hit a wall. Using a standard React app for Tauri (desktop) and Next.js for the web meant maintaining two entirely different architectures. Even though I was sharing UI components, I was essentially building and debugging two separate apps.
To solve this, I replaced the standard React setup in Tauri with Next.js (using static HTML export).
TNTStack is the result. It's a cross-platform monorepo template where both web and native(desktop & mobile) apps run on the exact same Next.js architecture. You write the core and ui once, and it builds for all platforms.
It’s a specific stack, but figuring out the configuration for this dual Next.js setup took a lot of trial and error. Hopefully, it saves someone else the setup time. I would love to hear your thoughts on this monorepo structure and the dual Next.js approach.
Project description: A monorepo template for building cross-platform apps. Write your code once and build for Web, Desktop, and Mobile.
What do you hope to build this month? I need to flesh out the landing page. Right now it only has a hero section, so I want to build out the missing parts (e.g Features, Pricing, etc. and a dedicated Download page UI) to make the template feel like a complete, out-of-the-box.
What kind of skills do you need?
Frontend skills (Next.js, React, Tailwind, Shadcn UI etc.) to help design and implement the landing page sections.
Anyone looking for an easy first contribution: helping tweak the documentation, or reviewing/fixing our i18n translations (currently have 10 languages generated via LLM, so native speakers fixing them or adding new languages would be amazing).
QA / Testers to install and test the compiled application releases (desktop, mobile) on different operating systems, as well as test the CLI tool used to scaffold the project.
The anxiety doesn't come from "missing out on code", it comes from the dread of waking up to a mountain of generated code that you now have to untangle and verify. Treating the AI strictly as a tool that gets turned off when I step away from the keyboard is the only way I've kept my sanity.
A couple days ago i search, is there any ide build with Tauri. Didn'nt see this. Great implementation. I like tauri and use my own projects too. I'm carious is realy enought as ide? i dont tested yet btw. but i will.
As a recommendation, replace screenshot in your readme with the code renderer view or etc. current looks ok but it could be better, i think.
That's when I hit a wall. Using a standard React app for Tauri (desktop) and Next.js for the web meant maintaining two entirely different architectures. Even though I was sharing UI components, I was essentially building and debugging two separate apps.
To solve this, I replaced the standard React setup in Tauri with Next.js (using static HTML export).
TNTStack is the result. It's a cross-platform monorepo template where both web and native(desktop & mobile) apps run on the exact same Next.js architecture. You write the core and ui once, and it builds for all platforms.
It’s a specific stack, but figuring out the configuration for this dual Next.js setup took a lot of trial and error. Hopefully, it saves someone else the setup time. I would love to hear your thoughts on this monorepo structure and the dual Next.js approach.
Repo: https://github.com/odest/tntstack
Live Demo: https://tntstack.odest.dev
Docs: https://tntstack.odest.dev/docs