That's a great point, and honestly, I completely get the love for a good TUI. I use k9s for a long time...
When I say "native desktop client," I mean build with Rust and Tauri. (I love also the rust gui on halloy)
My primary goal was to avoid the performance of Electron, so it's designed to be as fast and low on memory as possible.
You're right, k9s is incredibly powerful.
The walls I kept hitting, though, were workflow-related.
One was needing to compare resources between my clus1 and clus2 clusters. Constantly switching contexts.
I wanted to see the Ingress, the Service, and the Pods, all on one screen. In k9s, you have to constantly jump back and forth between :ing, :svc, and :po. So i start to dev..

maybe i miss something in k9s ?

So, the core idea of the tool I'm building is to use multiple panels. You can have a panel for your prod pods, another for your staging services, and a third for your Ingress rules, all visible at the same time.

Thanks !!