Because everyone wants their preferred set of tools/languages to do it using the design patterns they like and there is nothing wrong with that. I don't see myself using Beeware ever really but that doesn't mean people shouldn't work on it.
the last line of the comment you replied to gave a pretty good example: If you have tools build in tech X and just want to wrap them in a UI to make them usable on a phone. (similar to how Python ships with Tk bindings for UI: no, its not pretty, but it's an UI and thats what you want sometimes, without learning something big or worse a different tech stack)
This looks really good to be honest. So many projects I would have loved to create GUI's for and distribute that way but the overhead of having to sort out dependencies and packaging make it not feasible.
The key difference between Kivy and BeeWare is that BeeWare programs use the native UI toolkit of the platform they run on, whereas Kivy apps use a custom UI toolkit that uses the same controls across all platforms.
tifadg1 sums up my use case nicely:
> This is very interesting for someone who'd like to casually create a few apps on android for quality of life, but knows only Python and isn't interested in branching further.
I have some little python utilities that I’d love to have an iOS GUI wrapper for, but not enough to pay the $99 and learn something new.