Twitter | Search | |
Steve Troughton-Smith
It is such a shame Apple has decided to never open UIKit to watchOS devs, because now, thanks to new in-process dyld mechanics, it is easier than ever to load up a UIKit UI inside your watchOS app — mere header annotations the only blocker
Reply Retweet Like More
Steve Troughton-Smith Feb 6
Replying to @rgov
watchOS apps are two things, a container app stub, and the app extension that includes your code. Changes to watchOS over the years now mean it loads the extension inside the main app process instead of using XPC, which gives you direct access to the UIKit UI of the stub
Reply Retweet Like
Rody Davis Feb 6
Replying to @stroughtonsmith
Would this get approved if submitted? If you wanted to use a custom view for example?
Reply Retweet Like
Steve Troughton-Smith Feb 6
Replying to @rodydavis
highly unlikely that you could rely on it, even if they don't notice the first time
Reply Retweet Like
Ethan Feb 6
NSObject (no)
Reply Retweet Like
May🏳️‍⚧️ Struggle Tweets Feb 6
Replying to @stroughtonsmith
this looks like the 2010 ipod nano ui lmao
Reply Retweet Like
MacGyver Feb 6
Replying to @stroughtonsmith
Something to play with this wknd!!!
Reply Retweet Like
Zhuoli Li Feb 6
Replying to @stroughtonsmith
Agreed. WatchKit suck but SwiftUI on watchOS contains so many issues. See my privous hack (SPI) for WatchKit && AnimatedImageView(now removed)...
Reply Retweet Like