Any plans for a fcast sender App?
Hi,
First of all, I really like fcast. It is a really promising replacement for Chromecast, but it is unfortunate that there is only the (current) support for Grayjay. Are there any plans to release a counterpart, like a sender app for Android? It would be great to be able to share own videos, photos or even (for some people who prefer other YouTube clients like Newpipe) content to fcast via the "share" function like some UPnP apps offer. Are there any plans from your side?
Another completely different, but cool function, would be an integration in Home Assistant for my video doorbell.
Cheers and keep up the great work!
There are a few sender applications available such as a terminal client and a chrome extension (https://github.com/futo-org/fcast/tree/master/clients), but most development effort recently has been on improving the receiver apps and adding new platform support. In the future we will likely work on improving/adding new sender applications, but no current plans for developing an Android specific sender app.
More development effort however will first come to building out the FCast SDK and improving interoperability with AirPlay and ChromeCast. At that time we may try implementing a ChromeCast receiver within the FCast receiver so you can cast directly from ChromeCast -> FCast if feasible, and that would accomplish most of what an Android FCast sender app could do.
Hey Michael, thanks for your answer. Well, to use the correct wording, I will refer to client instead of sender app from now on. A basic function like the Chrome Extension or the terminal client for Android Devices via the share option would have been already a great start.
An another question: does "directly from ChromeCast -> FCast" means, that FCast would be a kinda dropin replacement for Apps with Chromecast support, but without using Chromecast?
I use on both ends 100% degoogled devices. My phone runs GrapheneOS and my Settop box is a Raspi 5 running Lineageos (ATV) without chromecast or any other Google shite.
Sometimes I use the terms client/sender interchangeably, but I believe the term 'sender' is more common. Regardless, feel free to use whichever term you like though.
An another question: does "directly from ChromeCast -> FCast" means, that FCast would be a kinda dropin replacement for Apps with Chromecast support, but without using Chromecast?
Yes, that would be the goal.
I use on both ends 100% degoogled devices. My phone runs GrapheneOS and my Settop box is a Raspi 5 running Lineageos (ATV) without chromecast or any other Google shite.
In this case you would have to wait until a sender app is developed for Android if ChromeCast is not supported on GrapheneOS. I too would eventually like to get around to supporting degoogled devices (I also use one myself), but we first have to improve the FCast protocol to support features like screen and image casting. After that, developing an Android sender app would likely be considered by then.
I've tried using this sender on Windows(https://github.com/MAlba124/OpenMirroring.git), and while it detects the official FCast receiver, it never works (opened this issue a while ago: https://github.com/MAlba124/OpenMirroring/issues/22). I'll try with Linux as a sender as well maybe tomorrow. Maybe you can play around with it and help contribute your experiences :)
I would also like to see an official FCast sender Android app, which will allow to cast media content from selected directory. Please make this happen 🥺
You talk about Chrome Extension, but what about Firefox?
You talk about Chrome Extension, but what about Firefox?
The current chrome extension has mainly been a prototype implementation, but its likely an official extension store listing would come at some point. Support for Firefox/Safari would probably be decided when we are working on it then.