Jonathan Willing

i will be at the mothership for WWDC tomorrow. hope to meet some of y’all there!

@kylebshr @mergesort A more resilient approach I like to use for components like this is to use Group(subviews:transform:) to resolve subview proxies, so you can check if the view is _actually_ empty (beyond just inspecting types). Unsure if that’s something a macro could help with — seems less likely.

@vanvoorden@mastodon.social we’ve certainly thought about it! we have some novel approaches to SwiftUI that I haven’t seen much of in the wild. maybe someday we’ll find an avenue to share more.

proud to have led the team on this. want to come build the next generation autonomous ride hailing platform? come join my team: apply or message me.

• ios: https://careers.withwaymo.com/jobs/senior-software-engineer-marketplace-booking-ux-ios-mountain-view-california-united-states
• android: https://careers.withwaymo.com/jobs/android-engineer-booking-mountain-view-california-united-states

next generation of Waymo booking flows rolling out.

lots of cool new tech here: flexible server-driven platform, fully native SwiftUI + Compose app components.

@schwa@mastodon.social secret hack they don’t want you to know: you can create a pseudo-lazy Layout by wrapping each individual subview in a LazyV/HStack.

the subview attribute graph is unfortunately still evaluated due to the nature of Layout, but the render tree is lazy.

@harshil@mastodon.social I tried and failed. the APIs just don’t exist.

the only option seems to be to use a UITabBar in a representable.

@axiixc@social.axiixc.com Hosting controllers work great for custom tab bars, but I feel one of the main draws for fully custom navigation stacks is matched geometry effects. Sadly, matched effects do not reach beyond their hosting container (namespace isolation?), so it doesn’t quite get the job done.

@axiixc@social.axiixc.com I enjoyed your recent SwiftUI wish list post! Nobody discusses container lifetime and it’s a very meaningful problem for those of us that are pushing SwiftUI beyond the basics.

I was hoping that the ContainerValues API (or the variadic API before it) would offer us more control over lifetime, but sadly it does not. When using it as a navigation stack, it keeps the state of the top-level View, but any subview state is lost — along with any scroll position (Apple folks: FB16459615).

@harshil@mastodon.social @khaost@mastodon.tz.is it’s definitely tempting, but I’m really hesitant about tying up such crucial data into a single ecosystem.