Among the many excellent H5 players such as Video.js, Xigua Player, and CKPlayer, why do we still choose to develop zwplayer? Our original intention is very simple: We want to help developers complete video playback integration more easily and efficiently.
Our team has been working in the multimedia field for over 20 years, witnessing the complete evolution from RM, WMV, MOV, to Flash (flv, rtmp), and now to H5 (HLS, DASH, WebRTC). We deeply understand the complexity and diversity of technical details involved, while most developers really need is just a simple, stable, and easy-to-use video playback solution.
Therefore, zwplayer's goal is very clear: minimize technical barriers. You don't need to deeply understand the differences between various streaming protocols like HLS and DASH, nor do you need to find and configure different playback plugins for different video formats. Regardless of what protocol or encoding format the video uses, you only need to provide a video URL, and leave the rest to zwplayer.
Developers need to choose different playback technologies and plugins based on video formats:
<!-- Playing HLS format -->
<script src="player-core.js"></script>
<script src="hls-plugin.js"></script> <!-- Need to load HLS plugin additionally -->
<script>
new Player({
element: '#video-container',
plugins: [HlsPlugin], // Need to specify plugin explicitly
url: 'video.m3u8'
});
</script>
<!-- Playing FLV format -->
<script src="player-core.js"></script>
<script src="flv-plugin.js"></script> <!-- Need to switch to FLV plugin -->
<script>
new Player({
element: '#video-container',
plugins: [FlvPlugin], // Need to change plugin type
url: 'video.flv'
});
</script>
<!-- Playing Dash format -->
<script src="player-core.js"></script>
<script src="dash-plugin.js"></script> <!-- Need to switch to DASH plugin -->
<script>
new Player({
element: '#video-container',
plugins: [DashPlugin], // Need to change plugin type
url: 'video.dash'
});
</script>Extremely simplified, automatically adapts to multiple video protocols with completely consistent API calls:
<script type="text/javascript" src="./zwplayer/zwplayer.js"></script>
<script>
// Playing HLS stream - auto-detection, no extra configuration needed
new zwplayer({
playerElm: '#video-container',
url: 'https://example.com/video.m3u8'
});
// Playing FLV stream - identical calling method
new zwplayer({
playerElm: '#video-container',
url: 'https://example.com/video.flv'
});
// Playing MP4 file - consistent API
new zwplayer({
playerElm: '#video-container',
url: 'https://example.com/video.mp4'
});
// Playing DASH stream - no code changes needed
new zwplayer({
playerElm: '#video-container',
url: 'https://example.com/video.mpd'
});
</script>Even for protocols not natively supported by browsers (such as RTSP), zwplayer can provide a consistent playback experience through the media gateway:
<script type="text/javascript" charset="utf-8" src="./zwplayer/zwplayer.js"></script>
<script>
new zwplayer({
playerElm: '#mse',
url: 'rtsp://admin:admin12345@192.168.1.64:554/Streaming/Channels/101',
xmc_url: 'https://xmc.zwplayer.cn:3006/'
});
</script>We are committed to building an intelligent yet foolproof player that allows developers to completely break free from tedious streaming media technical details and focus more energy on business logic and user experience optimization. Every minute you save is the embodiment of our value and the driving force for our continuous progress.
We sincerely invite you to experience the zwplayer! We have established a technical communication WeChat group. Welcome to add WeChat ID zwplayerX to apply for joining.
Any issues you encounter during use, feature suggestions, or format compatibility requirements can be fed back to us. We will respond promptly and continue to optimize, working together to create a more perfect playback experience.
zwplayer - Making Video Playback Simpler!