This is a worthy tradeoff! Phones are bigger than ever and scrolling is incredibly simple.
Scrolling may be easy, but it’s still harder to quickly skim content if you have to scroll more.
If you want to experience what your app is really like for the vast majority of real world people, go get a cheap monthly prepaid phone and try it out. Using the modern web on them is a complete nightmare. The screens are physically small and low resolution. The phone I had to use for a year and a half is 800something by 500something, which is literally first generation Android era resolution from over ten years ago. Information density matters. Huge buttons that get in the way are not merely frustrating, they are a design mistake and a demonstration that the designer is out of touch with reality, just as you seem to be here.
Please, get a crappy phone, get a crappy chromebook, make sure your app isn't frustrating to use for people that can't afford new, fast things.
https://news.ycombinator.com/item?id=44005192
This post is so god damn funny due to the lack of self awareness that this happened to them by virtue of being an engineer.
Amusingly, whoever made the blog post or perhaps the slide with the “4x faster” star seems to have doubled down on not caring about space allocated to content - the “4x faster” star also obscures the content!
I think it's completely okay to expect someone to have to learn a UI/UX if it is better in the long run (assuming it's not a product that gets used twice a year).
The prettier and more fun modern UIs get, the more I miss the UIs of the nineties. Controls looked like controls, screen space was well utilized, and even workflows that weren’t the most common were generally well supported.
<sarcasm>I suppose if an LLM writes your email for you, you don’t actually need to see all the text yourself.</sarcasm>