Jul 6, 2020

Live Streaming with Flutter and Wowza Streaming Engine

Learn how to use the Wowza Streaming Engine to create a live streaming platform.

Author

Vikram Pratap SinghVikram Pratap SinghSoftware Engineer
Live Streaming with Flutter and Wowza Streaming Engine

Flutter has been around for a while now and the ecosystem has been developing at a good pace. So, when I had the task to create a live streaming demo with Flutter, it was just a matter of finding the right tools and services.

For a complete live streaming app, we need two main things:

  • A live streaming service
  • A publisher

Live Streaming Service: It will run on the server side and will be responsible for re-encoding and making the video stream coming from a publisher accessible to anyone on the internet who has the correct URL and credentials.

Publisher: Any device or app that sends the video stream to the live streaming service can be called a publisher. In our case, our Flutter app will act as a publisher.

Setting up live streaming service

I chose Wowza Streaming Engine to use in my demo as it is very easy to set up and you get a huge choice of supported publishers to choose from.

To set up the Wowza streaming engine on Google Cloud, just follow this step-by-step tutorial. After it is done, we can access the Engine Manager web console on http://[external-ip]:8088/enginemanager, where external-ip is the public IP address of your Google Cloud Compute Engine instance. Sign-in to the console with the username and address that you provided and you’ll be provided with a screen like this:

Congratulations, you now have a Live Streaming Server.

Now let’s create a stream.

  • Go to Applications -> live. An application named live will already be created for you if you followed the instructions in the setup options correctly.
  • Click on Source Security in the menu on your left & disable all security on RTMP sources. We are doing this for the sake of ease. You can play around with different security settings later.
  • Now click on Sources(Live) in the same menu. You will be presented with a screen like this:

On the right under the Application Connection Settings section, you have some data that you will need while creating the publisher. Note down the following information:

  • Host-Server
  • Host-Port
  • Application

And that’s it for the server side, we are now ready to create a live stream of our own.

Creating Flutter App

  • Create a simple Flutter app or you can integrate in your existing Flutter app.
  • Add the dependency flutter_rtmp_publisher: ^0.0.1. You can choose from a large number of supported plugins, but I chose this as it needed no additional setup.
  • Add the relevant permissions Camera , Microphone , Internet in your AndroidManifest.xml for android and Info.plist for iOS.
  • In your Flutter app, create a button or any other widget that will trigger the streaming screen.
MaterialButton(

 child: Text("Start Stream",),

 onPressed: (){

  RTMPPublisher.streamVideo("rtmp://[Host-Server]:[Host-Port]/[Application]/myStream");

 },

),
  • Replace Host-Server , Host-Port and Application with the values that we obtained at the end of Setting up live streaming service section.
  • In the above code myStream is the name of the stream. You can use any name.

And that’s it. Your Flutter app is ready to publish. To check if it is working or not, just enter the same url rtmp://[Host-Server]:[Host-Port]/[Application]/myStream in any video player that supports RTMP streaming and you can see it live. Personally, I prefer to use HLSPlayer. You can paste the above link in the RTMP player tab there and now you have a complete live streaming application.

Here are a few points to keep in mind:

  • You can choose any publisher like WebRTC etc, Wowza supports almost all the popular options.
  • Don’t shy away from playing with Transcoder settings in Wowza Streaming Engine Manager to see what works best for you.
  • Google Compute Engine is not a free service, so don’t keep the instance running unless you are using it, otherwise you’ll incur charges. I learnt it the hard way.

That’ll be all. Peace.

Subscribe to Our Newsletter

RELATED ARTICLES

More from the engineering frontline.

Dive deep into our research and insights on design, development, and the impact of various trends to businesses.
The Bug That Doesn't Show Up in Code Review: Why Your Flutter Web App Reloads on Safari
The Bug That Doesn't Show Up in Code Review: Why Your Flutter Web App Reloads on Safari
A real-world look at how oversized images can trigger Safari reloads and iOS crashes in Flutter apps and how smarter image decoding prevents them.
From Prompting to Process: What Changed When Flutter Shipped Agent Skills
From Prompting to Process: What Changed When Flutter Shipped Agent Skills
This blog explores how Flutter Agent Skills improve AI-assisted development by combining official framework workflows with project-specific guidance for more consistent development.
Why Everything Your AI Builds Looks the Same
Why Everything Your AI Builds Looks the Same
This blog explores why AI-generated interfaces often look alike and explains how design systems, product context, and reusable engineering practices help teams build distinctive, scalable
How We Built the Missing Bridge from Code to Figma
Technology

Jul 10, 2026

How We Built the Missing Bridge from Code to Figma
This blog explores how AI-generated React apps get turned into fully editable, designer-ready Figma files by reading React Fiber instead of the DOM.
Building a Resilient Hybrid-Cloud Network with WireGuard HA, Route-Based Failover, and Deep Observability
Technology

Jun 27, 2026

Building a Resilient Hybrid-Cloud Network with WireGuard HA, Route-Based Failover, and Deep Observability
A practical breakdown of building resilient AWS-to-on-premises connectivity with WireGuard HA, active-standby failover, and deep packet-forwarding observability.
We Built a 114-Second AWS-to-Azure Failover. Here’s What We Learned
Technology

Jun 19, 2026

We Built a 114-Second AWS-to-Azure Failover. Here’s What We Learned
A practical guide to building a 114-second multi-cloud disaster recovery failover between AWS and Azure — what we built, what broke, and what we learned.
Cloud-Native and Cloud-Agnostic Are Not Ideologies; They Are Business-Stage Decisions
Technology

Jun 12, 2026

Cloud-Native and Cloud-Agnostic Are Not Ideologies; They Are Business-Stage Decisions
This blog explains how organizations can balance speed, scalability, and operational flexibility as they grow from startup to enterprise scale.

The Right Conversation Can Save You Six Months.

Whether you’re navigating AI adoption, modernizing legacy systems, or scaling a product - we start by listening. No pitch deck. No template. A real conversation.