I hope that future versions will merge the frontend and backend

[onlinedear]

I hope that future versions will merge the frontend and backend, allowing for a single client that can set various AI models, all of which can be configured directly on the settings page. Installing the backend is too difficult.

[onlinedear]

[sujithatzackriya]

Hello @onlinedear ,
I understand that it is a bit more complicated to setup the backend. As of now, we are working on making this better. The backend is made intentionally separated from the frontend to give the developers the ability to make changes to backend without breaking frontend.

Will definitely make the packaging process better for the backend. Thanks for sharing the screenshot for UI ideas. :) This is helpful. Currently working on the windows build. But let me see if we can make this UI change for ease of use.

I hope you were able to build the backend and run the tool. Please share the feedbacks like this.

Will keep this issue open and will close this once Frontend and backend is merged together. Have to port the backend to Rust and then merge them together.

[haroondilshad]

@onlinedear this looks like a neat graphic. Did you use an AI tool to create the UI mockup?

[maxdd]

I hope the backend remain under REST API since the machine running it should have the end goal to serve multiple clients.

[sazonovanton]

Is it possible to run frontend and backend on different machines right now?

[sujithatzackriya]

We are currently working on a configuration option to ensure seamless transcription and summarization even when the server (Backend) and frontend are running on different devices. This feature is expected to be released by the end of April 2025. @sazonovanton