Search Results for "client server"

live_svelte bridges Phoenix LiveView with Svelte components, letting you blend server-driven UIs and client-side interactivity in a single application. It mounts Svelte components from HEEx templates and wires props and events through a small interop layer, so data flows cleanly between LiveView assigns and Svelte state. The integration supports dispatching client events back to LiveView and pushing updates down to the component without writing custom glue for every case. ...

Phoenix LiveView is an Elixir library that enables rich, real-time user experiences by using server-rendered HTML over WebSockets, providing seamless dynamic interactivity without needing front-end JavaScript frameworks. It integrates deeply with Phoenix and ships by default in new Phoenix applications. LiveView brings a unified experience to building web applications. You no longer have to split work between client and server, across different toolings, layers, and abstractions. ...

Pusher server implementation is compatible with Pusher client libraries. Open Pusher implementation compatible with Pusher libraries. It's designed to be used as a single registered app with id, secret, and key defined on start. Poxa is a standalone elixir server implementation of the Pusher protocol. Docker images are automatically built by Docker Hub.

Fishjam is a real-time multimedia streaming toolkit for building low-latency video and audio applications. The GitHub repository refers to the original open-source Fishjam media server, which was a general-purpose media server written in Elixir and is no longer actively maintained. The broader Fishjam project has since evolved into a platform for WebRTC-based live video, audio, and messaging infrastructure. It is designed for use cases such as video conferencing, live streaming, classrooms,...

...Its structure showcases common concerns—authentication, profiles, content creation, feeds, tagging, and search—implemented with clean boundaries so features can evolve independently. Real-time updates and responsive interactions are handled using Phoenix’s live capabilities and channels, demonstrating how to mix server-driven UI with interactive client behavior. Background jobs, caching, and pagination patterns are laid out in a way that scales from small communities to heavier usage. The codebase emphasizes maintainability with clear contexts, test coverage, and a straightforward deployment story. As a learning resource, it helps teams see how to stitch together Phoenix primitives into a cohesive, production-leaning application.

...The library exposes desktop-specific affordances such as system tray menus, window management, and notifications, so applications feel native rather than like generic web wrappers. Because LiveView drives the UI, state lives on the server process, enabling real-time updates without heavy client frameworks. The result is a productive stack for tools, dashboards, and utilities where Elixir’s concurrency and resilience shine on the desktop. Teams get to reuse their Phoenix skills and still ship a polished native app experience.