Steve Troughton-SmithWith all the buzz about Final Cut, it sure would have been a good time for me to have had my clapperboard app ready to go, huh? 😒
I think I can take a sprint at this before WWDC, might make some progress. I have Freeform prepped, Xcode open. I have a bunch of things to do before I can get this to a shippable 1.0, including changing the core navigation & library structure, and removing all the SwiftUI I added in the early days. Fortunately, past-me was smart enough to port the whole project to Swift already, so it’s ready for me to pick up and run with it
Since I started this project in 2019, the design language I use in my apps has shifted a bit — and that of iPadOS, too. Restructuring it is kinda fun
If I'm to cut features to get to a ship target, it’ll primarily be by not including iPhone & Mac support at launch. Even so, I'll be progressing all three platforms at the same time as I go, as iPad still needs multiple resizable windows and compact/regular size class switching.
No platforms means I don't have to have a sync strategy out of the gate, too… 👀
🍌 Tim MahoneyYou going to WWDC? Want to talk about your future sync strategy?
@_tim______ unfortunately not! But if somebody were to, say, update the CloudKit GitHub examples with canonical ways of how to safely merge/resolve changes both ways after a device has spent time offline, I would be a lot happier to proceed 👀 That fear is a major blocker on several of my projects right now… https://github.com/apple/sample-cloudkit-privatedb-sync
I don’t blame you for being scared of that scenario.
What sort of data are you working with? Complex data types with complex merging strategies? Lists/graphs that the user can modify concurrently and expect them to merge properly? Or a more simple last-writer wins?
@_tim______ most of my data objects are flat by design; not expecting concurrent uses on different devices, but I do want to do the right thing if a device has been used without internet for a period. Last write wins is probably enough for individual record values. I just want to be able to do this w/o giving up and using Core Data 🥲 I wish there were a simplified record layer that 'just worked’ and didn't require antiquated boilerplate. There's a reason so many devs struggle with iCloud sync!