Hi the community, I like Tauri, and i want to use him everywhere! I think to start a new project which will be a little web browser. I am really curious about what do you think to start this kind o...
NLnet; Servo Webview for Tauri
The web ecosystem lacks a cross-platform, non-corporate controlled system for running web content. Tauri is a system for distributing cross-platform applications that relies on engines present on a system - effectively those owned by Apple, Google, and Microsoft. These permit varying levels of user control. The Servo project is a cross-platform, open source web engine.
Tauri vs. Electron: performance, bundle size, and the real trade-offs
A breakdown of the choice between Tauri and Electron for cross-platform apps, backed by practical comparisons and benchmark data.
tauOS
Discover the future of desktop computing with tauOS, currently in development. tauOS is designed with ease of use in mind, featuring human-centric design, an unbreakable core, and an syncing service that synchronizes files, configurations, keys, and more across all your devices.
GitHub - tauri-apps/wry at servo-wry-demo
Cross-platform WebView library in Rust for Tauri. Contribute to tauri-apps/wry development by creating an account on GitHub.
What Comes After Chrome
I co-created the world's most popular browser. Now, I'm joining The Browser Co to fulfill an old dream.
How Fugu is my browser?
The cross-company effort Project Fugu has the objective of making it possible for Web apps to do anything iOS, Android, or desktop apps can. Find out where on this exciting journey your current browser is!
The Architecture Of Local-First Web Development — Smashing Magazine
An honest perspective on building local-first web apps in 2026, written for developers who’ve been doing this long enough to be skeptical of silver bullets.
Announcing Supporters of Chromium-based Browsers
Since Google announced the Chromium project in 2008, we have been excited to build on the great foundations of open-source web browsers and contribute to the continued d…
How might a browser be developed?
There’s a confluence of things that have happened recently that have made me question how browsers might be developed: On January 8th 2026, Simon Willison predicted that someone will build a browser using mainly AI-assisted tools within 3 years On January 27th 2026, one human and one agent built a browser from scratch (great experiments) On the 19th February 2026, news came out that Taalas had a chip that can spit out nearly 17,000 tokens per second by baking a model onto the chip. I would like to indulge in a little bit of projection and in my case, some science fiction of my own.
The new Surf browser shows why everyone’s trying to connect AI to the web
A startup called Deta built a browser with a chatbot that can help you browse, organize, and understand the entire internet. It’s very cool.
Building on some of @chrisshank.com's work, what if we had browsers that were atproto-native? orange link = in your PDS green link = in the PDS of someone you follow Dreaming about the future of social hypertext ✨
𝕮
A web extension that colors any link you've saved on @semble.so orange.
Do people know I’m building an alternative to Electron and Tauri? Where you write typescript for the main and browser code and it just works. Has building, packaging, code signing, and update management built in. Bundles as small as 12MB and ship updates as small as 4KB? electrobun.dev
