I'm sorry for flooding your timelines all day but it's been so darn exciting! Tonight I'll go to bed not only having had a launch day that exceeded all of my wildest expectations, but I'll also have had Plinky cupcakes in my Plinky hat with a Plinky colored bouquet, courtesy of my perfect partner Colleen.
Hey internet friends ๐ค I have a big announcement to make and this time it doesn't have anything to do with apps ๐ค
Last month, our daughter was born and it is so incredible and wonderful to have her in the family now. I haven't been very active here nor done any work recently, as my wife and I were busy getting to know the little one and enjoying quality time to bond as a young family ๐งโ๐งโ๐ง ๐ฅฐ
PS: As many of you know I am very fond of dad jokes, so now I am officially entitled to make โem ๐
Customers sometimes report that our app's widgets are โstuckโ.
We handle this by wrapping every widget in a special URL modifier. It detects if the widget is in the โpreview" state. A widget should only be tappable in preview if the device JUST rebooted, or else it means widgets are broken.
If preview is detected, it sends a special deep link to the app. We show a message that tells the user to reboot. And if widget is fine? Then it applies the regular deep link URL instead.
By the way have you noticed widgets getting stuck after the app gets updated? Seems to be a frequent occurrence for me these days. Itโs not showing the preview, just stops updating.
@MuseumShuffle@rooster oh interesting, I wonder if itโs just a test flight thing. I think only people who have reported it were in TestFlight group (including myself)
I've been happily and successfully using CKSyncEngine in a new project that is local-first syncing with GRDB (SQLite). The one thing I'm not sure how to do though is handle failures. If CKSyncEngine tells me to something changed on the server and it fails on my end for whatever reason (so far, programming errors), I don't know how to tell the server and fetch those changes again. Anyone familiar with the right approach for that?
@zachwaugh do you have control over the change token? Youโd ideally be able to detect the error, throw, and discard the new change token (ie do not persist it). Then when app updates, you retry the read operation with the same change token that failed before.
Huh, I guess we can actually come quite close to replicating cellLayoutMarginsFollowReadableWidth in SwiftUI Lists now using safeAreaInset (and good olโ GeometryReader of course).
Exercise: four days of intense crossfit classes, probably the hardest I've ever worked out in one week
Home: made huge progress on backyard renovation plans
Espresso: got a bottomless portafilter and just made the best tasting espresso I've ever had
Foodnoms: getting close to finishing a big refactor that pays down some serious tech debt โ plus backend dev is getting close to finishing up an exciting new feature!
I've been experiencing knee pain (jumper's knee) on and off for many years. Thanks to a new routine developed following advice from my coaches, I've finally started making serious progress. Yesterday I was able to do barbell squats for the first time in years without ANY knee pain. I couldn't stop smiling, I was so happy.
Just completed another trip around the sun ๐ฅณ ๐ ๐
Fun fact: being born on 03/03 really helped when we moved to the US, as I never had to get used to entering my date of birth differently on forms, since MM/DD and DD/MM are the same ๐ค
FoodNoms just hit $200K net ARR (after app store commission) ๐ Crazy how this little app has continued to grow, seemingly against the odds. Especially proud of the progress made since I started working on it full-time a little over a year ago.
