OrchardNest

One of the things I was most surprised with when starting my iOS career was the lack of a backed-in, system-wide keyboard avoidance: every app needs to show a keyboard at some point, and every app has to either re-invent the wheel or pick...

When building new SwiftUI components, it’s common to offer variants for different purposes/screens.

Button is no doubt one of the most popular SwiftUI elements, it’s also very special, as it is the only component with two different style protocols: ButtonStyle and PrimitiveButtonStyle.

Every time we create a new view, we’re defining a new API: regardless of whether those views will be used just by us or by several people around the world, it’s very important to keep all definitions consistent.

When displaying text of various lengths, our design needs to be clear on whether there should be a maximum number of displayable lines, or if the full text should always be shown.

2020 didn’t go as planned, it came and went, but boy was it a tough year for everyone.

Apple has recently published some great new articles around building layouts with SwiftUI’s stacks in various situations.

Shout out to Mike Ash for the original, historic Let's build NSObject article.

For a great overview on SwiftUI navigation, please check out this article by Paul Hudson.

Like any other Swift framework, SwiftUI heavily relies on protocols as a core part of its definitions: in previous articles we’ve covered examples of SwiftUI’s own protocols such as View or LabelStyle.

In Adaptive SwiftUI views we’ve covered many approaches on how to make our layouts responsive to different external factors such as size classes, dynamic type, and more.

Many thanks to Stefano De Carolis for the tip!

In Composing SwiftUI views we’ve covered an example on how to start building a design system, and how it’s very beneficial to have one as early as possible in any project.

We’ve previously covered how to add optional bindings to SwiftUI views using DisclosureGroup as an example.

One of the most powerful aspects of SwiftUI is how it adapts based on the context: this is SwiftUI’s promise, running on all Apple devices, from the 38mm Apple Watch to the 27-inches iMac (without considering external monitors!).

We’re tasked with building a brand new iOS 13+ app, or, maybe, with migrating an app from UIKit to SwiftUI: where should we start?

Many thanks to @kingatarthur for the tip!

A couple of weeks ago I’ve updated AStack, a micro library that switches any SwiftUI stack axis when the environment content size category is among the accessibility ones.

One of the new SwiftUI components from this year is Label. The SwiftUI team did is a great job with Label’s documentation: if you’re not familiar with this view yet, please have a read at it first.

When defining a SwiftUI view, it comes automatic to write struct MyView: View followed by var body: some View { ... }: all our views are composed by other views, but at some point SwiftUI needs to draw something on the screen: when does it...

SwiftUI’s PreferenceKey declaration is as following:

When working with SwiftUI views, sometimes we would like to apply different modifiers based on conditions/states:

Searching online for “SwiftUI ScrollView offset” yields to plenty of discussions on how to control the scroll position of a ScrollView: with iOS 14 SwiftUI has gained ScrollViewReader, covered here, which makes the old introspection hacks...

Article inspired by Mauricio Meirelles’s GridView.

SwiftUI views layout depends on each view state. This state is composed of a mix of internal properties, external values coming from the environment, etc.

@AppStorage and @SceneStorage are two SwiftUI property wrappers that have been introduced this year.

With the recent release of Xcode 12 we’ve gained a new .redacted(reason:) SwiftUI modifier.

This year we’ve gained new SwiftUI features designed for WidgetKit: let’s explore what they are.

Among the SwiftUI enhancements from this year, List has learned to traverse hierarchical data.

When SwiftUI launched, one of the missing pieces was the ability to programmatically control the offset of ScrollViews: in Xcode 12 and iOS 14, we’ve gained ScrollViewReader, which addresses exactly this shortcoming.

Among the new SwiftUI views from this year WWDC we have DisclosureGroup: DisclosureGroup shows/hides its content based on a disclosure state:

As a university student, there hasn’t been a day where I came back home without plenty of new, lengthly notes from all the classes I attended.