SwiftUI Defaults Considered Harmful
tonsky.me
SwiftUI Defaults Considered Harmful
1–10 of 135 posts
Re: SwiftUI Defaults Considered Harmful
#2I’m guessing the magic layout things are intentional because SwiftUI is designed to make it easy to have one app feel native on iPhone, iPad, Apple Watch, Mac and AppleTV, which all have their own design language and ergonomics.
As long as it provides ways to override defaults and take full control where needed, this seems reasonable. I’m guessing you can drop a Metal view into your SwiftUI app, so quit complaining :)
Re: SwiftUI Defaults Considered Harmful
#3I tried out SwiftUI a couple of months ago and it was buggy even when sticking to the standard Navigation components..
But now it seems like a lot of problems have been solved
https://stackoverflow.com/questions/59279176/navigationlink-...
Re: SwiftUI Defaults Considered Harmful
#4I’m guessing the magic layout things are intentional because SwiftUI is designed to make it easy to have one app feel native on iPhone, iPad, Apple Watch, Mac and AppleTV, which all have their own design language and ergonomics. As long as it provides ways to override defaults and take full control where needed, this seems reasonable. I’m guessing you can drop a Metal view into your SwiftUI app, so quit complaining :…
Exactly, if you just want to bang something out that looks like an "apple app" across all those devices I think the auto spacing and sizing stuff works pretty well. You can always tighten it up and override it later.
Re: SwiftUI Defaults Considered Harmful
#5I tried out SwiftUI a couple of months ago and it was buggy even when sticking to the standard Navigation components.. But now it seems like a lot of problems have been solved https://stackoverflow.com/questions/59279176/navigationlink-...
I had this issue in the simulator but on my phone it seems fine. Not ideal obviously but it does work, I released a simple app with it earlier this year.
Re: SwiftUI Defaults Considered Harmful
#6This website's background color is considered harmful, and "considered harmful" essays are considered harmful.
Re: SwiftUI Defaults Considered Harmful
#7This website's background color is considered harmful, and "considered harmful" essays are considered harmful.
Site is also non-responsive with , looks horrifying on the 12.9’’ iPad Pro even without taking color scheme into account. I know complaining about blog design is out of scope, but if @tonsky is reading this thread, please consider fixing your meta viewport tag.
Re: SwiftUI Defaults Considered Harmful
#8I tried out SwiftUI a couple of months ago and it was buggy even when sticking to the standard Navigation components.. But now it seems like a lot of problems have been solved https://stackoverflow.com/questions/59279176/navigationlink-...
> even when sticking to the standard Navigation components.
The standard navigation components have always been the buggiest part of UIKit. Don't even get me started on how UISearchController and UINavigationController interact on iOS 13…I have an app that's been sitting on the back burner, with full dark mode support, but unreleased for over six months because I haven't taken the time to figure out why the search bar decides it wants to be above the large title.
Re: SwiftUI Defaults Considered Harmful
#9This website's background color is considered harmful, and "considered harmful" essays are considered harmful.
Site is also non-responsive with , looks horrifying on the 12.9’’ iPad Pro even without taking color scheme into account. I know complaining about blog design is out of scope, but if @tonsky is reading this thread, please consider fixing your meta viewport tag.
> I hope you have a wide enough monitor to read this.
Perhaps they're merely unaware of how their website looks?
Re: SwiftUI Defaults Considered Harmful
#10Earlier quoted context omitted.
Site is also non-responsive with , looks horrifying on the 12.9’’ iPad Pro even without taking color scheme into account. I know complaining about blog design is out of scope, but if @tonsky is reading this thread, please consider fixing your meta viewport tag.
> I hope you have a wide enough monitor to read this. Perhaps they're merely unaware of how their website looks?
This part also tripped me up since I _was_ on a large monitor but the width was tiny.