u/carlievanilla

If you've used AVPlayer, the mental model here will feel familiar. We open-sourced MoQKit, a native SDK for MoQ (Media over QUIC) with Swift APIs for iOS (Kotlin for Android too). It plays broadcasts, publishes camera/mic/screen, and carries app-defined data tracks, all over QUIC. Ships as a Swift Package.

(disclosure: I work at Software Mansion / Fishjam. MoQKit is ours and open source)

The shape: a Session owns the relay connection (think AVPlayer's connection state) while a Player owns rendering, except one Session can fan out into many players, publishers, and raw data tracks at once. The API is async/await, with a ~100ms target buffer on playback. If you already have your own capture or render pipeline, you can publish from any source conforming to FrameSource instead of being forced through the built-in camera/mic classes.

Honest status: it's 0.2.0, and we'll break the API the moment MoQ does (it currently targets moq-lite, a more stable profile than the still-moving moq-transport draft). It's usable for real workflows today though.

Repo: https://github.com/software-mansion-labs/moq-kit

Blogpost: https://fishjam.swmansion.com/blog/moqkit-native-mobile-sdk-moq-ios-android

Point the demo at the hosted relay https://moq.fishjam.work/public and start in Player mode.

I know Elixir-in-production stories are always a good read here, especially when they're about a brand you actually recognize. So here's one: we (Software Mansion) spent a good chunk of this year contributing to Logflare, the log + metrics platform that runs inside Supabase's infra. It's a big distributed Elixir app processing a lot of data, so most of the interesting problems are the "this runs on every event" kind. Sharing the parts that were fun from an Elixir angle.

• The rules tree. Every log event gets matched against a set of user-configured routing rules. The old code walked the full rule list for every event. We rebuilt it as a tree that prunes branches that can't match early, so only the relevant rules get checked. Closer to logarithmic than a linear scan, which barely matters in a dev env and matters a lot at Supabase's volumes.
• BigQuery export. It was sitting on a deprecated legacy REST API. We moved it to Google's gRPC Streaming API. More compact payloads, less outbound traffic per event, faster, and at this scale that's a real GCP bill reduction.
• Export adapters. Added adapters to ship logs to external services (Axiom, Last9, and OTLP so anything speaking OpenTelemetry works). That meant refactoring the adapter system so adding destinations isn't painful, which ended up being the groundwork for Supabase's Log Drains. Later added connection testing so you can check a destination works before streaming to it.

Separately, on the JS side, we also migrated realtime-js off Supabase's long-diverged Phoenix.js fork onto canonical Phoenix.js (it's a thin wrapper now instead of a fork someone has to maintain), plus some React Native reconnection hooks. Less Elixir-relevant, but if you've ever subscribed to a channel and wondered what's underneath, it's Phoenix channels over WebSockets.

Full write-up with the Supabase team's comments: https://swmansion.com/case-studies/supabase/

We've integrated Gemma 4 into react-native-executorch. You can now run it fully offline in your React Native app, with GPU acceleration via the Vulkan delegate on Android and the MLX delegate on Apple Silicon.

Full release note

See the demo

We spent a few months building scalable server-side live compositing and hit every wall you'd expect.

At some point we listed out all the annoying properties and went "wait, this is just an FPS game server." Same constraints almost down the line. So instead of being clever we just stole the game infra playbook: Anycast to grab a nearby node, latency-sensitive inputs/outputs go straight to the node's unicast IP, boring HTTP through the load balancer, warm pool sitting ready so nothing cold-starts.

Full story here: https://fishjam.swmansion.com/blog/live-video-compositing-devops

(heads up, I work on this at Software Mansion, so I'm obviously a little biased)

Quick one: the CFP for RTC.ON (video engineering conf in Kraków, September) just got extended to June 7.

Disclosure – I'm on the organizing team, so this is partly a heads-up and partly a "please submit, we'd love talks from this community."

Details at https://rtcon.swmansion.com/#call-for-papers. AMA in the comments if useful!