With the rising popularity of social voice platforms such as Clubhouse and Twitter Spaces, it is high time for an Open Source alternative. A platform like this would not only enhance credibility within the open-source community, but also attract more users and foster growth. An engagement platform that is Open Source has the potential to drive significant traction and help establish a strong presence.
- Design and Develop a Flutter Mobile Application.
- Develop a backend for the app using NodeJS, Firebase and LiveKit.
- LiveKit - It is an open source WebRTC stack that gives everything needed to build scalable and real-time video, audio, and data experiences in our application. This will be responsible for audio streaming. It will be easier to implement and deploy it since they have a great documentation too. To get started, we can use their free cloud service and then we can host the open-source version on our own server.
- Firebase - We can use it for storing user data, managing rooms/spaces (Firestore Database).
- Auth0 - Will be used for authentication of users.
- NodeJS - Will be used to develop a web server which will interact with the mobile app, firebase as well as LiveKit. The flutter app will interact with the server using REST API endpoints.
- Flutter - Will be used to develop the application for various platforms. We can design the app using MVC (Model View Controller) architecture and use GetX for state management. GetX offers several features, including reactive programming, dependency injection, and routing, which can help us build scalable and maintainable application. Listeners, moderators and speakers are devices having the flutter application.
Please join the discussion in this issue
Flutter will be used to develop the application for various platforms. We will be designing the app using MVC (Model View Controller) architecture and we will be using GetX for state management. GetX offers several features, including reactive programming, dependency injection, and routing, which can help us build scalable and maintainable application.
Make sure to use conventional commit structure as follows:
<type>: <short summary>
│ │
│ └─⫸ Summary. Not capitalized. No period at the end.
│
└─⫸ Commit Type: docs|feat|fix|perf|refactor|test