FreedomDesktop

FreedomDesktop is where you work. It wraps the web apps you already use, strips the bloat, bridges their data, and adds real-time collaboration — all over an encrypted mesh network.

What It Does

Imagine opening your tools for the day — not in browser tabs, but in panels. Side by side. Draggable splitters between them. Like VSCode, but for web apps instead of code files.

Each panel loads a third-party web app (TPA): your MLS, your tax assessment site, Google Maps, your CRM, DocuSign. But FreedomDesktop owns the browser, so it can:

• Inject CSS — strip navigation, sidebars, ads, footers. Show only the core UI and data.
• Inject JS — extract hidden data: JSON payloads, server-rendered HTML, form values. Data the app has but doesn’t expose.
• Bridge data — when you click a property in MLS, the address flows to the map, the assessment, the CRM. Automatically. No copy/paste.
• Share the view — your colleague sees the same panels, same data, same state. Their cursor appears on your screen. You chat. You video call. All in the same view.

The TPAs don’t know they’re inside FreedomDesktop. They think they’re in a browser tab. But you’ve taken control.

The Key Insight

“Don’t build a web scraper. Enhance a real user sitting at a real browser.”

A webview IS a real browser. Every TPA serves its full DOM, all hidden JSON, all server-rendered data — because you’re a legitimate, authenticated user. There is no anti-bot, because there is no bot. You own the browser. Not the other way around.

This was proven with a working prototype that extracted full property data from Realtor.com and Zillow — not by scraping, but by simply reading what the browser already had.

TPA Recipes

A recipe is a small file that describes how to clean up and connect a specific app:

Recipe: BC Assessment
├── CSS: hide header, footer, sidebar
├── Extract: address, assessed value, property ID
└── Events: fire "property_selected" when user clicks a result

Recipes are the community contribution. Someone writes a recipe for Zillow, shares it with their group, and now everyone’s Zillow panel is clean and bridged. AI can write recipes — “write me a FreedomDesktop recipe for DocuSign that extracts signing status.”

No app store. No approval process. No SDK to learn. If you can write CSS and a bit of JS, you can write a recipe.

Who Uses What

The same FreedomDesktop, different recipes:

User	Panels
Real estate agent	MLS + BC Assessment + Maps + CRM + DocuSign
Lawyer	Case management + Court filings + DocuSign + Email
Wedding couple	Pinterest + Venue site + Google Sheets + Canva
Small business	Invoicing + CRM + Project manager + Calendar

The panel layout, the data bus, the collaboration — all identical. Only the recipes change.

Self-Created Apps

One of your panels doesn’t have to be a TPA. It can be a local HTML file — a custom tool you built, or had AI build for you.

Someone creates a showing scheduler with Bolt or Cursor. It’s just HTML/JS/CSS. Drop it on your group’s lighthouse. It runs as a panel alongside your TPAs. Same data bus. Same collaboration. Just another panel.

This answers the “then what?” problem: AI tools let anyone build an app, but deploying it requires hosting, auth, networking. In FreedomCore, you drop an HTML file and your group can use it.

The Architecture

FreedomDesktop
├── System tray (always running, mesh connected)
├── Panel manager (draggable splitters)
├── TPA panels (each a webview)
│   ├── CSS injected: strip chrome
│   ├── JS injected: extract data, listen for events
│   └── Data sent to bus
├── Data bus (Go backend)
│   ├── Receives data from any panel
│   ├── Broadcasts to other panels
│   └── Sends to peers over FreedomMesh
├── Collaboration overlay
│   ├── Chat
│   ├── Video (WebRTC over mesh)
│   └── Multi-user cursors
└── FreedomMesh (Nebula, encrypted P2P)

Platform Strategy

Platform	Technology	Status
Windows/Linux	Go + Wails v3 (target)	Wails v2 functional, v3 evaluation next
macOS	Swift/SwiftUI + Network Extension	Build 17, TestFlight live
Browser	WebRTC gateway (zero install)	Planned
Android	VPN Service	Scaffolded
iOS	Network Extension	Deferred

FreedomDesktop has been through a decade of iteration: Electron, Pear/Holepunch, Tauri, jQuery, Polymer, Vue, Svelte — each promised productivity but delivered learning curves. The current approach: vanilla HTML/CSS/JS for the frontend. Platform-native shells. No framework tax.

Why the App Matters

In the A2A model, the application IS the security perimeter. FreedomDesktop is the only software that can talk on FreedomMesh. This means the app controls what capabilities are available, who can access what, the trust context, and when access ends.

If you only control the network (like Tailscale), you encrypt the pipe but have no control over what flows through it. If you only control the app (like Slack), you rely on someone else’s network. FreedomCore controls both. That’s the point.