Over the last few weeks, I’ve been working to do two things on the WastedTime set of apps. (Wow! I can say set of Apps now).

While the basic functionality is working on all three platforms, iOS, macOS, and WatchOS, I am not happy with the behavior of SwiftUI to render the various graphics. SwiftUI has introduced some really cool images with the SFSymbols library, and using those simplifies the sizing of elements across platforms.

Well, not really, given that SFSymbols is not really supported correctly on macOS. So that means that my buttons to add and remove attendees in a meeting cannot be the same on macOS. That wouldn’t be a problem, if SwiftUI would allow me to use the Image() for buttons. My plan was to go back to my original images used in the iOS app, and just leverage them for the macOS version. Nope – they don’t render at all.

So, I decided I would go back and start working on the Twitter integration instead. This seemed like it would be pretty easy, since I had that working fine using TwitterKit on iOS for years now.

Well, not really, given that Twitter discontinued that service… So, I would have to try and use a new library. I decided to try Swifter. I had heard good things about this library, and they support both iOS and macOS. While I setup the code to enable Twitter and to create a Tweet, nothing happened. Evidently, you need to setup a callbackURL to leverage the new Twitter serviced. Having not dealt with callbackURLs at all, I took to StackOverflow to get more information. Net-net, there is no information. So, go to the gitrepo for Swifter, and again, no help. So I posted an issue to the repo, and have been in a wait state until I hear back.

Guess, I am going to have to do a lot more reading and learning. More to come…