It’s called user experience. Just as important as functionally
If they’ve used colour assets in their library then for iOS devices it is literally just as simple as setting the colours that you want dark mode enabled on as ‘Color.primary’ and that will switch between light and dark dependent on the system setting.
No, not really. I develop iOS/macOS software and assuming they’ve used the new framework, it is very easy. Even if they haven’t used the new framework, then it doesn’t take much longer.
Why would Apple make it difficult for developers to support dark mode when it came out nearly two years ago? Literally as simple as using primary colours.
Fellow app developer here. I think you’re oversimplifying the issue here. For a lot of apps, using iOS system UI components, it’s as simple as toggling an option and Apple does it for you, since they control the palette.
Monzo, for a large chunk of the app, don’t, and some of their components that are designed to look and feel similar are actually quite hacky adaptations.
Monzo for the most part would need to build their own palette, and test it rigorously for accessibilty, which often can go overlooked by many developers. It’s an important and time consuming aspect to consider, so you don’t wind up disadvantaging those who are colour blind for example, or have issues with certain levels of contrast. Beyond a moral responsibility, there are legal ones here too. For a lot of indie developers using the frameworks, Apple does all this work for them. Monzo will need to do this for themselves, which is a downside of going beyond native UI frameworks.
None of this of course excuses how long it’s taking them. They could have done this years ago, before iOS even had the option, then very quickly adopted the system level toggles for activation. Monzo are the epitome of slow in the fintech world these days. But I’d rather slow and right than rushed and sloppy.
But yes, you are correct, if you wish to alienate and potentially be sued by some of your disadvantaged users for not catering to their needs, as is Monzo’s responsibility. I think it’s bad practice to oversimplify the issue in this way.
Wouldn’t the standard theme be an option for those with visual impairments though? Although I suspect there are people with visual impairments that might already struggle with Monzo’s current theme yet I don’t think they’ve been sued, unless we’re saying Monzo’s current theme works for everyone and is some how perfect?
The app theme choices will be ‘Dark’, ‘Light’ and ‘Use device settings’ - and then a sub-set of choice-of-dark will be ‘Lights out’ (black) and ‘Midnight Sky’ (dark) - it can’t be far off at this point
Anyway… All votes and discussion needs to happen in the below main topic - no point diluting it all here where it’s likely to go unnoticed.
I believe they have been testing dark mode for a few months now. So hopefully it will be rolling out next year in the first few months
Whistle, pause, whistle, “Easy now, eeeaaassy”…
I mean it works. There are a good number of folks who find light themes very hard on their eyes even on the lowest possible brightness. Depending on the day, I have to wear sunglasses, have the brightness way down, and have night shift turned on for a more comfortable viewing experience else I risk a migraine. Which sucks because I personally prefer white themes, especially outdoors. Night mode outright prevents this for me, so I turn it on in those instances.
Just because no ones taken an accessibility issue that far yet, doesn’t mean there’s no precedent for it. Especially in the US where folks are more willing to sue over issues like this.
Interesting article on this stuff here, as attention and expectations have shifted dramatically in recent years, and applies to app design just as much as it does to the web:
technically not true for all iPhones
also not true
I guess there are a number of possible reasons Monzo haven’t released an app with dark mode.
- It’s not possible - unlikely.
- It’s incredibly difficult - maybe.
- It’s fairly straightforward, but they haven’t time - could be.
- It’s really easy, but they don’t want to - unlikely.
Take your pick.
Can I add my own?
- It’s not that difficult to do, more difficult to do properly, and with less staff, it got bumped down a priority list
- There’s a spider on the developers desk so the build is currently on hold.
- Bingo the dog ate their work.
Dark Mode Strings are still in the latest version of the app:
<string name="app_theme_dark_theme_title">Dark theme</string> <string name="app_theme_subtitle_battery">Set dark mode to follow the Battery Saver feature located in your device settings</string> <string name="app_theme_subtitle_system">Set dark mode to follow the light or dark theme setting located in your device settings</string> <string name="app_theme_title_dark">Dark</string> <string name="app_theme_title_light">Light</string> <string name="app_theme_title_system">Use device settings</string> <string name="dark_theme_name_black">Lights Out</string> <string name="dark_theme_name_dark">Midnight Sky</string> <string name="settings_theme_title">Theme</string>
So not just a Dark Mode, but 2 modes - one darker than the other. And selectable device setting and/or battery saver mode too. Not sure if extra/updated code is needed to enable it or if it is already done and it’s just a server-side switch , but ‘Theme’ will turn up in Settings* at some point
*I don’t think it’ll land in Labs first, given that last string
I think its more of a case of lets not actively pursue it but once you come to make changes to a screen then add it the changes to allow it to be switched on.
Easier to justify that way that adding a purely superficial update when other things which are way more important can be done
The approval for transactions page is still white even with dark mode