Super Platform History

Purpose

Prox OS is not the first attempt to make software feel like a unified working environment. The useful question is not "who had the biggest vision?" but which parts of those visions became daily tools, which parts stayed too abstract, and which lessons should shape a browser-based OS Space platform today.

This note is intentionally high-level. It does not try to be a complete history or a precise timeline. It is a product memory map for building Prox OS with less amnesia.

NLS and the Mother of All Demos

Doug Engelbart's NLS and the 1968 demonstration showed a dense bundle of ideas: mouse input, hypertext, windows, shared screens, collaborative editing, outlining, and networked knowledge work.

The important lesson is that a platform is not only a set of apps. It is a way to augment human thought. The interface, linking model, collaboration model, and working memory all matter together.

For Prox OS, this argues for surfaces that help users reason across apps, documents, sources, and AI context instead of treating every app as a sealed box.

Project Xanadu

Project Xanadu pursued a deeper hypertext vision: durable links, bidirectional references, transclusion, versioning, and a global knowledge fabric. Some of those ideas remain more ambitious than the mainstream web.

The lesson is double-edged. A coherent information model can be powerful, but a huge perfect system can fail to become a daily product. Users need incremental value long before the full world model is complete.

For Prox OS, the narrow wedge should avoid requiring users to understand every future object type. Links, Spaces, and app surfaces must feel useful first.

Lotus Notes and Domino

Lotus Notes and Domino made enterprise groupware practical: mail, databases, documents, workflows, custom apps, replication, and organizational collaboration.

Its lesson is that platform value often comes from workflows and adoption channels, not visual novelty. Enterprise systems win when they match how groups actually coordinate, approve, archive, and repeat work.

For Prox OS, the App Store and Surface Runtime should not only look beautiful. They should eventually help a team package repeated work into Spaces, apps, permissions, and context that can be reused.

Groove Networks

Groove explored secure team workspaces and distributed collaboration. It treated the workspace as the primary collaboration container rather than only a folder or chat room.

The lesson is that Spaces are powerful but need distribution, trust, and clear workflow entry points. A Space without a daily reason to open it becomes a concept, not a habit.

For Prox OS, Proxied Spaces and future OS Spaces should always answer: what can a person do faster today because this Space exists?

SharePoint

SharePoint became an enterprise collaboration platform through intranets, document management, permissions, lists, search, and deep Microsoft integration.

The lesson is that enterprise platforms win through integration, governance, identity, and adoption channels. The "workspace" is only credible when access, ownership, compliance, and migration paths are boring enough to trust.

For Prox OS, permission modeling, app contracts, source connectors, and readable docs are part of the product, not back-office chores.

Google Wave

Google Wave combined ideas from email, chat, docs, wiki pages, real-time collaboration, bots, gadgets, and federation. It was ahead of its time in many ways, but adoption struggled because the product introduced too many new mental models at once.

The lesson is not "ambitious collaboration is bad." The lesson is that users need a familiar path into unfamiliar power. If a product requires a new noun, a new verb, a new workflow, and a new social protocol all at once, most people will return to their old tools.

For Prox OS, each new surface mode must be anchored in a known mental model: desktop, launcher, canvas, grid, IDE, or immersive app.

ChromeOS, webOS, and Firefox OS

Web-first OS attempts proved that the web can carry more of the operating system experience than traditional desktop software once assumed. They also showed that hardware distribution, app ecosystems, offline behavior, permissions, and system integration are much harder than a good UI prototype.

The lesson is that an OS story needs distribution and trust. Browser-first is a strong starting point, but it cannot pretend to have every desktop or device capability.

For Prox OS, the current product should remain honest: browser shell first, PWA next, then possible extension and desktop-client helpers.

PostHog and modern product OS inspiration

PostHog and similar modern workbench products show how a complex product can feel like an operating system without claiming to be a hardware OS. Apps, dashboards, insight tools, feature flags, product analytics, and settings sit inside an opinionated product surface.

The lesson is that a strong product surface can make complex tools feel like one system. The OS metaphor becomes useful when it helps users switch context, compose tools, and understand where work lives.

For Prox OS, Desktop Surface Engine is a way to make that composition explicit: the same app can appear as a window, card, node, grid widget, IDE panel, or immersive surface.

Puter and browser desktop projects

Puter and other open-source web desktop projects show that browser-based OS interfaces can be real software, not just novelty demos. Files, apps, windows, settings, and cloud-like runtime concepts can all exist in a web app.

The lesson is that differentiation matters. A web desktop alone is not enough. The product must explain what only this OS-like layer makes easier.

For Prox OS, the answer should be OS Spaces, app publishing, surface manifests, Switchbar routing, AI-readable context, and a growth path from personal shell to team platform.

WebCatalog, Atlas, and Spaces

WebCatalog and Atlas are useful references for turning web apps into manageable assets and organizing them into workspaces. That influence matters, but Prox OS should not become a clone or a copied catalog.

The lesson is to absorb the product pattern, not the database. Third-party sites can be searchable and manageable, but browser iframe limits, site policies, and future client boundaries must stay visible.

For Prox OS, this reference becomes one layer inside a wider OS Space platform, not the whole strategy.

Product Takeaways

• A platform needs daily wedge value before it earns the right to reveal its full model.
• New mental models should be introduced through familiar surfaces.
• Spaces need workflow gravity, not only visual grouping.
• App contracts, permissions, and docs are product features when AI agents and third-party apps are part of the platform.
• Browser-first must be honest about browser limits.
• Surface Runtime is valuable because it lets Prox OS grow beyond a single windowed desktop without pretending every mode is production-complete today.