User Profile

In my traditional Swift/UIKit applications, I use IQKeyboardManager to make sure that the on-screen keyboard does not obscure the text field (or text view) being edited.What is the situation in SwiftUI? Is this something that is part of the "it just works" part of the framework, or do I still have to implement it? And if the latter, any thoughts as to how to approach the problem?Thanks,Rick Aurbach

Let's suppose I want to provide a new user with some sample data which they can use to familiarize themselves with my app. In the NSPersistentContainer (i.e., local-only) case, I use one-time initialization logic to manually populate my app with this sample data. Then, over time, the user can keep that data, modify it, or delete it, as they choose.Now if I want to do the same thing with NSPersistentCloudKitContainer, this should be fine with my user's first device. But let's further suppose that (after using my app [and changing the CoreData database contents), my user load my app on a second device and runs it. On the second device, it will ALSO build an initial database containing sample data.What happens now? Does the content of the second device superceed the contents of the first? Suppose the user deleted a same record on device 1, but that sample record is loaded onto device 2 (as part of it's one-time initialization). Does that record reappear on device 1? And if a sample record is modified on device 1 (but appears initially unmodified on device 2), what happens? Who wins?What is the "best practices" technique for dealing with correct synchronization of a new device (that contains sample records) with the iCloud store?

I am beginning work on my first SwiftUI application, which uses CoreData as its data-store. And I have an issue I'm having trouble wrapping my head around.If I use an @ObservedObject property wrapper on a CoreData record, then use $property to bind an attribute in the record to a UI element, I understand that this sets up a two-way binding, which is good.BUT, in the case of a non-modal view, what strategies are recommended for knowing when to save context?Let me demonstrate my ignorance. This example is based on what I think I know (which is likely completely wrong):@ObservedObject var obj: MyCoreDataObject var body : some View { Toggle(isOn: obj.$active) { Text("Is it active?") } }Because of the binding ($active), the value of the toggle and the attribute in Core Data object ought to be synchronized. But if the user actually taps the toggle, thus causing the obj.active attribute to change, that change needs to be saved. So, what are some ways to make sure that happens? Or have I missed the point?Rick

I have some custom controls I developed in my traditional Swift/UIKit applications and am thinking about migrating them to SwiftUI. However, the controls are currently iOS-specific. When implemented on macOS, I'd probably choose a different approach.I have yet to see any guidance (from Apple or from the numerous SwiftUI blog posts) as to the best way to approach building a custom control that have device-specific implementations.Can someone offer guidance or suggestions for getting started? I'm assuming that the solution is to provide device-specific conditional compilation, but a list of which methods need to be overridden would be a great start.Thanks,Rick Aurbach