MōBrowser, a TypeScript-first desktop app framework with typed IPC
Details
- External ID
- 47766955
- Source
- HN
- Company
- —
- Product
- MōBrowser, a TypeScript-first desktop app framework with typed IPC
- Website domain
- teamdev.com
- Launched
- April 14, 2026
- Cohort
- —
- Upvotes
- 7
- Upvotes percentile
- 0.38817480719794345
- Tags
- —
- Fetched at
- Sept. 7, 2026, 9:26 p.m.
- Updated at
- Sept. 7, 2026, 9:26 p.m.
Description
Hi HN,For the last ~15 years I've worked on embedding web browsers into Java and .NET desktop apps (JxBrowser, DotNetBrowser). Over time, I watched many teams move from embedding web views into native apps, to building full desktop apps with frameworks like Electron and Tauri.Both are useful, but in practice I kept running into several problems.With Electron, beyond the larger app footprint, I often ran into: - lack of type-safe IPC - no source code protection - weak support for the modern web stack Tauri solves some problems (like app size), but introduces others: - different WebViews across platforms → inconsistent behavior - requires Rust + JS instead of a single stack So we built MōBrowser, a framework for building desktop apps with TypeScript, Node.js, and Chromium.Some of the things we focused on: - typed IPC using Protobuf + code generation (RPC-style communication instead of string channels) - consistent rendering and behavior across different platforms - Node.js runtime - built-in packaging, updates, and scaffolding - source code protection - small delta auto-updates The goal is to let web developers ship desktop apps with a web stack they already know and fewer cross-platform surprises.I'd especially love feedback from people who have built production apps with Electron or Tauri.Happy to answer any questions.
Enrichment
- Theme
- browser automation and scraping for AI
- Vertical
- Horizontal
- Function
- Dev tools
- Audience
- Developer
- AI stance
- Not AI
- Project type
- Commercial product
- Normalized one-liner
- typescript desktop app framework
- Manually corrected
- False
Could you build this?
No Building a custom cross-platform desktop runtime embedding Chromium/WebViews with type-safe IPC across multiple OSs requires deep native systems programming (C++, Rust) and OS-level windowing experience.
What it would actually take: This framework requires native C++ or Rust bindings to Chromium (CEF) or native platform web engines, implementing custom multi-process architectures, window management, and native OS message loops on Windows, macOS, and Linux. The hard part is building reliable, zero-copy, typed binary IPC serialization between V8 isolates and native processes while ensuring thread safety and sandboxing. It requires senior systems software engineering experience in browser internals and desktop framework architectures.
Discussion
No comments on this launch.
Competitors
Other products that read as similar to this one — 145 launches clear the similarity bar, closest 8 shown.
Attention rank: #90 of 146 (itself plus its competitors, highest first — normalized so YC and Product Hunt are compared fairly).
Launched 162 days after the earliest competitor.
- GrainJS · hn · 2025-12-26 · 5 upvotes · similarity 0.44
- Mystral Native · hn · 2026-01-27 · 50 upvotes · similarity 0.41
- Ant · hn · 2026-07-11 · 330 upvotes · similarity 0.41
- Treenix. Typed runtime for humans and agents · hn · 2026-06-15 · 5 upvotes · similarity 0.40
- Nectar, a Rust-like React that compiles to WebAssembly · hn · 2026-07-06 · 29 upvotes · similarity 0.40
- SharpTS · hn · 2026-01-09 · 6 upvotes · similarity 0.40
- Rune · hn · 2026-06-07 · 5 upvotes · similarity 0.39
- Monghoul · hn · 2026-05-13 · 6 upvotes · similarity 0.39
Other launches for this product
- No other launches for this product.
Same idea, different domain
Nobody's really built a dev tools tool for Sales yet.