PC Bridge
The problem
People using locally hosted apps need a practical way to reach them from another device while the host computer is running.
Evidence & constraints
A local prototype and automated checks exist. Phone access, a real target app, WebSockets, and app isolation have not been verified. Registered apps share a browser origin; use only mutually trusted, non-sensitive apps. An installer, automatic startup, and native desktop streaming are not implemented.
What we are trying to do
Build a private, usable bridge from a Windows computer to a phone for selected local web apps, and verify it with real devices and applications.
Measured impact
No verified outcomes have been published. Activity and contributions are not a substitute for evidence of benefit.
Technical architecture
An original Node.js host with a local app registry, access-key sign-in, a mobile web portal, and a proxy to selected loopback web apps. Private remote access currently requires separate networking software.
Roadmap
No approved milestones yet. Establish evidence, agree requirements, complete verification, and secure pilot consent before deployment.
Read the nine-stage project lifecycleSource repositories
Contributors
No contributors are recorded for this project.
Stewardship
No maintainers have been appointed. Acceptance requires named stewardship, review capacity, and a succession plan.
Open work
No contribution tasks have been published.
Deployments
No operational deployments are recorded.
Documentation
The institutional guides define our requirements for accessibility, security, review, and maintainership.
Open the contributor handbookDecision records
No project decisions have been published.
Funding
No funding or expenses are recorded for this project.
View the public ledgerOpen by default
Software license: MIT. Data, research, hardware, and documentation need an appropriate artifact-specific open license. Contributions do not confer ownership of the institution.
Licensing guidance