kat

eBay developer APIs are difficult but I’m figuring them out. This app is very information dense so a lot of the time spent has just been getting a semblance of UI for testing, and getting ways to put in all of that information first. For example, I had to find a data source of all CPUs, find a good NLP model to get CPUs out of the page, go on a side quest getting access to eBay APIs, and I still don’t have it making any decisions based off of that data yet!

watchOS complications haven’t been working until now. Accessing SwiftData inside watchOS complications is annoying, and the solutions online don’t seem to take into account recent *OS changes. What ended up working was storing a reference of the database inside the widget extension. This is genuinely most of what I worked on for 5 hours I’m slowly going insane

Base functionality of the app, before flavortown started. Architecture uses SwiftUI on both the iOS app and companion watchOS app. iOS app allows you to store schedules and classes (functionality like to-dos, calendar will occur later). It then stores in SwiftData and syncs to the watch with Watch Connectivity, where the watch will also save it in it’s copy of the SwiftData db and set up the complications as necessary (the main watchOS component right now).