WARD GEYS↖ Back to portfolio

CASE STUDY / WARDOFLIXDESKTOP + WEB

WardoFlix

Press play.
Keep it simple.

A personal streaming client with a cinematic interface and a media engine underneath. Browsing, playback, subtitles and resume history belong in one experience.

Read-only WardoFlix interface export. Sample profile.
Read-only WardoFlix interface export. Sample profile. Explore the interface
Platform
Windows desktop · installable web app
My role
Interface, AI-assisted implementation and iteration
Stage
Personal project · desktop version 1.7.8
The actual WardoFlix browse interface, with catalog artwork and metadata from TMDB and a demonstration profile. This is a read-only view; playback is not connected. Open full size ↗

THE STARTING POINT

The interface
is only half of it.

I wanted a media app that felt good to use: pick a title, choose how to watch it and return to the same place later. The visual side drew me in. The playback problems made it a much deeper project.

A source can have the wrong video codec, several audio tracks or subtitles that drift. WardoFlix brought the catalog interface and the Node streaming service into the same build, so I could work on the whole path to the player.

HOW IT WORKS

Behind the
play button.

The media pipeline decides how to deliver a source the browser can actually play.

  1. 01

    Inspect

    The service checks the source’s container, video codec and available audio tracks.

    NODE / EXPRESS · FFPROBE
  2. 02

    Prepare

    Compatible media can play directly. Other sources are repackaged or transcoded as needed.

    SOURCE HANDLING · FFMPEG
  3. 03

    Play

    The player presents video, track controls, subtitles and the viewer’s saved position.

    VIDEO.JS · REACT

INSIDE THE BUILD

Small details.
A better evening.

Pick up where you left off.

Local profiles keep viewing history, watched flags and resume positions separate. Continue Watching gives that stored state a useful place in the interface.

Sound and subtitles count.

Audio-track selection, subtitle language and timing adjustments sit alongside the player. Codec handling and stereo downmixing help bridge the gap between a source file and Chromium’s playback support.

One interface, two ways in.

React powers the Windows Electron app and the installable web interface. Desktop packaging uses an NSIS installer, with update handling in the application. The project also includes DLNA and Chromecast support.

The hard part happens
after you press play.

WHAT THIS PROJECT TAUGHT ME

A polished browse screen is not enough. Seeking, subtitle timing, unsupported codecs and interrupted streams all shape whether the app feels dependable.

WardoFlix became a place to work through those details, from the React interface to the server and the Windows installer. It is a personal project, with its browsing interface shown here using catalog data and a demonstration profile.

NEXT PROJECT / ATLAS STORY STUDIO

Another problem.
Another build.

Explore Atlas Story Studio