Build calling into your app
Use an AI coding agent to scaffold a small meeting room, add calling to an existing app, or prototype an Electron workspace. Freehop provides the same JavaScript API and TypeScript declarations whether you write the code yourself or pair with an agent.
Freehop does not ship an AI model, hosted assistant, transcription pipeline or agent runtime. If your platform needs summaries, a copilot or moderation, choose and connect those services in your own application. Keep provider secrets on your backend and make any sharing of voice, video or messages with an AI service explicit to participants.
A build brief you can use
Build a small browser meeting room using Freehop.
Read Freehop's Quickstart, TypeScript guide and public client API before writing code.
Use freehop@alpha and keep the interface and connection layers separate.
- Use the bundled types; narrow incoming message data before reading its fields.
- My backend authenticates users and issues session tickets.
- Start with microphone and camera off. Enable each only after a click.
- Attach incoming media tracks to my own HTML call panel.
- Support chat with small, validated messages, below 20 per second.
- Show the actual path: direct, gateway, relay, bridged or unreachable.
- If I configure a TURN relay as a last resort, my backend passes it in tickets (createAuthority({ turn })); never hard-code TURN credentials in the page.
- Handle missing permissions, blocked playback and connection failures.
- Leave the session and stop owned media on navigation.
- Keep keyboard controls, labels and mobile layouts usable.
- Test two independent browsers, peer departure and media shutdown.
Do not invent SDK methods or claim production reliability.
Do not put authority secrets, provider keys or gateway signing keys
in the browser. Do not add an AI service or upload media by default.
Start with the Quickstart, TypeScript guide, client reference and use-case recipes. A build brief is a starting specification; review the resulting code and test it on your target devices and networks.
Build the platform you have in mind
| Idea | Freehop’s role | Your application supplies |
|---|---|---|
| Small meeting room | Human voice/video, chat transport and device controls | Room UI, invitations and admission |
| Shared creation workspace | People talking inside the canvas | Editor, persistence and collaboration model |
| Electron community app | Session client and optional desktop gateway | Accounts, navigation, packaging and updates |
| Human + AI support room | Human participants and media controls | AI integration, consent flow and moderation |
Keep the integration reviewable
Check that every generated method exists in the SDK reference. Validate incoming messages, test reconnect and leave flows, and inspect what network requests the app makes. Publish the alpha limitations alongside your prototype.
For a concrete foundation, remix Hopper for small rooms or the live demo to inspect the calling layer. The SDK, protocol and examples are open source; you can inspect the whole path from a Join action to a peer connection.