Write it as a CLI first, if you can. Python with rich (for output formatting) is a great choice. But if you have appropriate tools, working with what you're comfortable with is a great choice too.
Until recently, I was in a similar situation. I had an idea of what I wanted to do. I had some prototype code written up as a web app in JS. It was going to be this beautiful thing that would help so many people.
But then I realized it was too much pressure. I wanted this for myself more than anything else. So I sat down and hammered it out in python in an afternoon. (Full disclosure, python is my main language, and I already knew exactly what this thing needed to do. I also found a library that did the Hard Part for me.)
And the best part: when I tell certain people about what I built, they don't care that it's a janky CLI. They're just happy they don't have to build/commission it themselves.
Embrace jankiness and get something working. You'll have fun.
Until recently, I was in a similar situation. I had an idea of what I wanted to do. I had some prototype code written up as a web app in JS. It was going to be this beautiful thing that would help so many people.
But then I realized it was too much pressure. I wanted this for myself more than anything else. So I sat down and hammered it out in python in an afternoon. (Full disclosure, python is my main language, and I already knew exactly what this thing needed to do. I also found a library that did the Hard Part for me.)
And the best part: when I tell certain people about what I built, they don't care that it's a janky CLI. They're just happy they don't have to build/commission it themselves.
Embrace jankiness and get something working. You'll have fun.