Currently, there’s an official PeerTube app, but I have been wondering if they should instead potentially consider an alternative strategy similar to what Lemmy has done.
The proposal is this:
Instead of maintaining an official PeerTube app, what if PeerTube focused instead on being the core system and API, while encouraging third-party developers to create various client apps?
PeerTube could then concentrate on managing and improving the web app, api, etc.
Potential benefits of this approach:
- Diverse ecosystem of apps catering to different user preferences
- Reduced workload for the core PeerTube team
- Increased community involvement and innovation
Potential drawbacks:
- Lack of a “standard” mobile experience
- Possible fragmentation of the user base
- Quality control challenges
What are your thoughts on this idea? Would this approach better serve the PeerTube community and align with the project’s goals? How might this impact PeerTube’s growth and adoption?
I think PeerTube has an API. I haven’t looked at it, but they have quite an extensive documentation and connectors to programming languages like Kotlin:
https://docs.joinpeertube.org/api/rest-getting-started
This might have been done already.