I notice that

    Syncthing-For
    k
is one of the first pieces of text in the first screenshot. With the k on its own line like that. Not usually something I’d comment on, but if you’re showing off a redesign…

That app itself also has some of the most revolting UI I've seen in a modern Android app (Vertical gradient filled buttons with thick gray strokes surrounded by not-quite-Material UI widgets, in a nonsensical custom control they had to go out of their way to make rather than just use a dropdown). Android developers really just don't care.

Or putting `Installed apps` under `Settings`. Still not fixed after 15 years.

System app list is doing almost anything you need for installed apps, I don't think I needed the list in fdroid once in my life.

its not an app you open much. I'd prefer them to spend time on the actual functionality

Good design is part of the functionality.

What word would you use to differentiate design and non-design functionality?

[flagged]

bc android users are less picky

All designers only use Mac+iOS. /s

There's so much worse out there. This at least looks functional and shouldn't hurt anyones' eyes.

Anyway, this is a FOSS project. Anyone could go and work with them to clean up the design.

Honestly I'd take that over the hostile vomit that is the google playstore. That thing is an offence to my senses...so many colors and animations trying to grab my attention.

"F-Droid 2.0: better than hostile vomit"

^ 2026 in a nutshell

It's annoying and easy to forget, but you have to enable the high-quality line break algorithm per Text component in Compose. Or you have to set two flags (maxLines=1 and overflow=TextOverflow.Ellipsis). I usually end up with a TitleText and BodyText component in my codebases that set these flags internally so I don't have to remember.

I wasn't sure if this was a joke about Android being unintuitive so I was sad to see that enabling high quality line breaks is indeed something you have to configure:

https://developer.android.com/develop/ui/compose/text/style-...

That document literally says that high quality option is the default.

No, it doesn't. It says:

> Should be a default

Meaning the developer should opt-in to this explicitly but choose it as the default option. The actual default is no strategy at all.

But it's a fork, isn't it?

Yeah, even AI could tell this design is not really polished.