Explore >> Select a destination
|
You are here 
|
kenb.us | ||
| | | | |
www.iamsim.me
|
|
| | | | | This will be the first in a - hopefully - long series of posts about building a UIKit app using The Composable Architecture, developed by Brandon Williams and Stephen Celis of PointFree.co fame. If you do not subscribe to Point-Free I highly suggest you take a look at some of the free episodes to get you started. If you'd like to sign up, here's a referral link that'll give me some credit! | |
| | | | |
sintraworks.github.io
|
|
| | | | | In this post we will create a SwiftUI control that can be popped up from the bottom of the screen. We will also make it possible to allow a specific view (usually the view that triggers the control and reflects the chosen value) to be raised, if it would otherwise be obscured by the control when the control pops up. This post assumes you have a reasonable knowledge of SwiftUI and are at least somewhat familiar with more advanced topics such as bindings, geometery readers, preference keys, etc. It won't go into details as to how they work. I will simply show how to use them to achieve the desired effact. | |
| | | | |
www.highcaffeinecontent.com
|
|
| | | | | ||
| | | | |
noahgilmore.com
|
|
| | | It's been a year since SwiftUI was released, and many iOS developers who are lucky to only support the two most current iOS versions will soon be able to start writing SwiftUI in their production apps. There are clear benefits to using SwiftUI (I could probably devote a whole post to them), so the question I've been thinking about is: where to start? | ||
