Round off buttons 'pill style' like on the website/server

[AndyScherzinger]

With the server progressing towards a design change (among other changes) regarding the buttons nextcloud/server#11943 - we can adopt that one too ;)

• Round buttons are defined within Material Design in the "Crane Design" see https://material.io/design/material-studies/crane.html

• These "new" buttons or rather the different new styles for buttons are implemented via the new MaterialButtons which deprecate the existing AppCompatButtons, see https://material.io/design/components/buttons.html in general and https://material.io/develop/android/components/material-button/ for API

• To be able to make use of these new implementations we need to move away from the Android Support Libs to the successor AndroidX, which @tobiasKaminsky already started working on here Switch to AndroidX #3089

• requires Switch to AndroidX #3089

Pinging @tobiasKaminsky and @nextcloud/designers @jancborchardt for feedback. While due to the requirement (#3089) we can't tell when this issue can actually be tackled, still wanting to start the discussion now :)

[nextcloud-android-bot]

GitMate.io thinks possibly related issues are #2835 (Button style and layout), #2697 (Panic button support), and #1028 (Cannot authenticate to this server).

[tobiasKaminsky]

To have it consistent between web ui <-> Android I am totally fine with this.

[tobiasKaminsky]

If you want, you could already start with this @AndyScherzinger.
Just base off from my #3089 branch.

[AndyScherzinger]

If you want, you could already start with this @AndyScherzinger.
Just base off from my #3089 branch.

Nice! I'll see if I find the time. Can't say how many layouts we have where we would need to change this :) Other than that, would we also like to move on to a then "newer" Android font which is a bit more round-ish (as used by the Crane theme) which is also kind of aligned with Nc15 server where a font change will happen? See used font by Crane: Raleway --> https://material.io/design/material-studies/crane.html#typography

[tobiasKaminsky]

Seems to use a bit more space…

Can't we use the same as server?

As I understand from https://blog.stylingandroid.com/android-o-fonts-part-2/ we could use Typeface support, but then would have to do code changes.
On the other hand we can explicitly say which font to be used, but this then needs to be done on every UI element (though I guess we can define it in styles).

[tobiasKaminsky]

https://fonts.google.com/specimen/Nunito

[AndyScherzinger]

We could define it in styles, but... we need to go for Android v15 which is exactly why I proposed to stop supporting Android 4.0.x since proper font support is only available with Android 4.1. We can use it for v14 but then need to do this programmatically polluting the code base just to support v14 which is probably what you are referring to with "code changes" as for the layout files, yes we might then have to do this per layout, thus if so we should do it in a separate PR.

[tobiasKaminsky]

Can't we use version depending styles? Same we have in https://github.com/nextcloud/android/blob/572ff509431ca344b0266644960a41b8ad3aa988/src/main/res/values-v19/styles.xml

Then we would have the new font for >= 5 and once we drop support, we can move style definition.
Polluting the code with all those font definitions and checks for version is nothing I would like to have in…

[AndyScherzinger]

I am fine with having this as a v15 or v19 refresher for the design