Rumble StudioSole iOS developer2023 – 2026
Go Live from the phone, on infrastructure we already had.
Studio let creators multistream from a desktop. Creators wanted to go live from their phone. I shipped “Go Live!” on iOS by pointing the app at Direct RTMP, the pass-through pipeline Rumble had already built for OBS, instead of building a mobile pipeline of our own.
Streaming Platforms
Problem
Going live meant a desktop, an encoder, and a stream key. Creators on the move couldn’t.
My part
Sole iOS developer. I owned Go Live from design handoff to the App Store, working with the backend and design teams.
Hard call
Don’t build a mobile streaming backend. Direct RTMP already passed a stream through untouched. Make the phone speak it.
Result
“Stream live directly and seamlessly right from your phone, with chat on screen.” That’s from the App Store release notes.
What creators needed
Studio’s pitch was multistreaming: go live once, reach Rumble, Locals, YouTube, Twitch, Facebook, and X. By 2024, 2,000+ creators had adopted it, among them Tucker Carlson, Megyn Kelly, and Donald Trump Jr. The desktop room did a lot (canvas, overlays, guests). The phone needed one thing: a fast way to be live.
How the pieces connect
Direct RTMP rooms are persistent and use a static key, which is what makes them good for a phone: the app can keep one room and reuse it every time, and the creator never sees a stream key. The phone pushes the stream, and Studio multicasts it to every destination the creator turned on.
Dependencies I coordinated
Backend owned the room and the multicast. Design owned the camera UI. I owned everything on the device and the contract between them: when the room is created, when the key is fetched, what the app does when a destination fails mid-stream.
Every Apple screen
I built Studio for iOS from scratch and shipped every update on iPhone and iPad. The same iPad app runs on Vision Pro, with custom UI so eye tracking can highlight each control.