While there is much to be gained from this lesson, I feel like it would have been nicer if, again, they had followed the paradigm from Landscapes. It is nice to read code, but if that is the point, why go through the trouble of making an Xcode project & scrollable sliding detail? It looks fabulous but at the end this lesson is in fact a walkthrough.
This was interesting, though:
Could the same code entered in a different approach on separate machines render something different?
Does this question make sense?
Choosing the right way to hide a view felt like a sticky pad with the text .opacity( 🙂 ✅
I want to take a moment and shout out another dev, Diego Lavalle for the article https://swiftui.diegolavalle.com/posts/linewrapping-stacks/. I had an issue which I was trying to grapple and this post gives me ideas on how to solve it.
Scaling Views to Complement Text I spent a lot of time reflecting on. Why? I was working on a problem around Accessibility and edge cases. On my ExitRowUI the circles would remain the same size as the Dynamic Type got larger, then if there are several trains at a particular station (Times Sq, Atlantic Av), the text inside would be clipped. The user would not be able to tell what they are seeing: it was just a circle with clipped text inside. This led me to tinkering with Label and reverting back to Text after noticing the content was no longer centered when I changed to Label. I did some digging and just like Diego made me imagine a solution to this problem on my ExitRow, I found a snippet from Apple in LazyHStack documentation that solved the problem in a different way.
mvilabrera 