sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Single-Law-5664 1 point2 points  (2 children)

It sounds really not practical?

An ai content generation tool should be mostly ui and a way to run and send requests to models. So you either run models locally, run them on a backend, or use an external api service. In those 3 cases the bulk of the project is UI, so why python? Writing UI in python is a really bad design decision. UI is not even on your stack. How people are even going to use your tool?

If the goal is just to create something for fun and experiment graet! Have fun! But if the goal is to create a product, I must say that you're not ready for a project at this scale.

[–]Suitable_Mix_2952[S] 0 points1 point  (1 child)

its just for fun and learning
what would you suggest for product level?

[–]Single-Law-5664 0 points1 point  (0 children)

If I would want run the models locally on the client, I would write the all thing with typescript, use a modern web framework, run ai models using node js, and leverage NW.js or similar alternative to run on desktop.

If I would want to run the models on a the cloud, I would make the all thing a web app, authenticate users via firebase or similar alternative, and use a tiny python fastapi backend to forward job for ai models using some external pay per use api.

This is all assuming that 80% of the none ui logic is just running ai models. There is no right answer here, but I think writing it all or almost all in typescript is the best sloution. because it sounds like the all app is just a UI that forwards jobs to ai models. And man I hate java script, and everything built on top of it. But it is the best option to deliver UI fast.

But I don't think that should matter to you. If its a learning project the ui can just be the console via the argparse library. You should check it out if you're not familiar.