4 ms·

I have some conflicted feelings on this, I feel like this should be controllable as a user and not blockable by developers. My single biggest pet pieve with my

I have some conflicted feelings on this, I feel like this should be controllable as a user and not blockable by developers. My single biggest pet pieve with my iPhone is when a developer (Google is a big offender) decides that instead of sticking with native design language they are just going to steamroll their own design language onto a device it wasn't meant for. I feel like consistency goes a long way towards a better computing device.

shkkmo 3y ago
Then you agree with this letter. It is calling put a specific issue and currently the only way to fix it would be to take away user theming by hard coding a stylesheet. Since that removal of user choice is antithetical to these developers, they are looking for better solutions. One solution is asking distributors to not apply themes to apps by default without doing QA on those apps. The other solution is to provide apps a way to opt out of system default themes without those apps having to remove user choice by hard coding the stylesheet.
- nerdjon 3y ago
  There is a third option and to me is likely the better option. The themes are applied by default but there is somewhere to easily disable it on a a per app basis by the user and not by the app developer. This makes it so some consistency is the default option but if something breaks then you can disable it. Maybe throw in some user education if you are really worried about this. Edit: Also to be clear I don't really agree with the article. I understand some of the points it makes but considering downloading an app and it having a different UI is a frustration for me I would be very happy if on my iPhone I could somehow overwrite parts of that UI. (Ultimately right now I just uninstall it)
  - shkkmo 3y ago
    I think the UX of requiring users to opt out of untested and likely broken themes on a per app basis is bad. I think an opt-in via prompt on first run (or whatever) is a better experience since it makes the distinction clear in case stuff breaks and provides an opportunity to warn users about potential breakage.

shkkmo 3y ago

Then you agree with this letter. It is calling put a specific issue and currently the only way to fix it would be to take away user theming by hard coding a stylesheet. Since that removal of user choice is antithetical to these developers, they are looking for better solutions. One solution is asking distributors to not apply themes to apps by default without doing QA on those apps. The other solution is to provide apps a way to opt out of system default themes without those apps having to remove user choice by hard coding the stylesheet.

nerdjon 3y ago
There is a third option and to me is likely the better option. The themes are applied by default but there is somewhere to easily disable it on a a per app basis by the user and not by the app developer. This makes it so some consistency is the default option but if something breaks then you can disable it. Maybe throw in some user education if you are really worried about this. Edit: Also to be clear I don't really agree with the article. I understand some of the points it makes but considering downloading an app and it having a different UI is a frustration for me I would be very happy if on my iPhone I could somehow overwrite parts of that UI. (Ultimately right now I just uninstall it)
- shkkmo 3y ago
  I think the UX of requiring users to opt out of untested and likely broken themes on a per app basis is bad. I think an opt-in via prompt on first run (or whatever) is a better experience since it makes the distinction clear in case stuff breaks and provides an opportunity to warn users about potential breakage.