vega-org/vega-app

Vega App is aimed at Android users who want one player for their own local and remote video files and who care about casting to a TV without losing subtitle or audio-track control. The practical case is narrow but real: you have a file or a provider source, and you want it on a bigger screen with your preferred audio language and subtitles intact.

The problem

Watching a downloaded or remotely hosted video on a phone usually splits into two workflows: a local player for the file and a separate casting route for the TV. The casting step often drops embedded subtitle or audio tracks or forces an external player, so the user ends up switching apps and manually hunting for a subtitle file. Vega changes that step by combining playback, casting and track selection in one app, and adds a watchlist, download handling and external player/downloader support. The result is one place to pick a source, play it locally, or send it to a Cast/DLNA device while keeping the tracks you want.

What's different

The casting implementation is the part worth noticing: the README describes a custom remuxer for Google Cast and DLNA that supports changing embedded audio and subtitle tracks project instructions. That matters when a container's tracks are not directly playable by the receiver, because the app can repackage the stream rather than discard those tracks. Vega also exposes provider sources and custom plugins, alongside sync with a desktop app, so the same library and source setup can extend beyond the phone. The trade-off is that this is a media-source-agnostic shell: the project states it does not host, store or provide any content, and all content is managed by the user through third-party tools or integrations project instructions. The experience therefore depends on sources and plugins you supply, not on a built-in catalogue. Casting and remuxing also add moving parts that a plain local player avoids.

Who should try it

Good fit: an Android user with their own video files or provider sources who regularly casts to a Google Cast or DLNA TV and wants embedded audio and subtitle tracks to follow the stream. The desktop sync and plugin support are relevant if you already manage sources in a companion setup. Poor fit: someone looking for a ready-made streaming catalogue, since the app deliberately ships no content and expects you to configure providers provider guide. It is also a weaker fit for casual phone-only viewing, where the casting complexity buys nothing. The build path is a separate consideration: the README documents a React Native/Expo build from source React Native environment guide, so tinkerers who want to modify the app can do that, but ordinary users are expected to install a release build.

Requirements and limitations

This is an Android application, distributed through Google Play, GitHub releases and the project website project homepage; there is no documented iOS path. Casting requires a Google Cast or DLNA-capable receiver on the same network, and the custom remuxer is the feature most likely to determine whether a given file plays with its tracks intact, so test with your own container formats rather than assuming universal compatibility. Content setup is on you: providers are added via a separate guide and the app takes no responsibility for what those sources deliver. Building from source means setting up a React Native environment, installing dependencies and running an Expo prebuild for Android, then signing the APK/AAB per React Native's instructions React Native environment guide. That is a developer workflow, not an install step, and it requires ongoing attention when dependencies or the React Native toolchain move.

HotRepo's take

HotRepo has only one dated observation: on 2026-10-26 the project appeared on the daily trending board with 1,628 stars and +11 that day. With a single recorded date, persistence of interest cannot be judged, and the 913-day repository age says nothing about maintenance quality. The decision-relevant question is narrower: check whether the custom remuxer handles the specific containers and embedded tracks you actually cast, and confirm the provider setup path matches what you can supply.