\n<\/p>\n
In the last two weeks since my device arrived, I\u2019ve had a blast going through apps in visionOS. Thanks to everyone who sent me a link<\/a> to your app, too.<\/p>\n I\u2019m no expert yet, but I\u2019ve spent some time thinking about the potential of visionOS as an app platform in the last couple of weeks. The first conclusion I\u2019m ready to draw is that there are two types of apps:<\/p>\n The App Store has plenty<\/em> of apps that are good to use if you already have the headset on, and I\u2019m quite sure this is due to SwiftUI. The effort of adding one more platform to a multi-platform SwiftUI app isn\u2019t enormous, especially if the app already supports iPad. But with that ease of development comes the downside. Your app already exists on other devices! So, if someone needs your app, they\u2019ll pick up their iPad or phone (which they are probably already holding) before the Vision Pro.<\/p>\n Whereas if they are already wearing their Vision Pro, having your app on visionOS is a great benefit. I\u2019d much rather open a native app than look through the passthrough cameras to use it on another device. So, the first thing I\u2019d say is it\u2019s definitely worth adding a visionOS version of your app if it\u2019s not too much trouble. \ud83d\udc4d<\/p>\n But those apps are not going to make the platform a success. visionOS needs apps that will make you walk up or down a flight of stairs, take your glasses off, and put the headset on for a chance to use them.<\/p>\n The good news is we have several years to make those apps happen, and it\u2019s not solely up to third-party developers either. Apple needs to put plenty of work into clearing the \u201cCompatible Apps\u201d folder out. They also need to ship many more apps that make this device shine. The hardware is more than capable and when it gets it right, it really gets it right!<\/p>\n But until Apple releases those apps, do you have an idea for an app that will make people put their headset on?<\/p>\n Dave Verwer<\/p>\n Building chat and struggling with state, push notifications, and more? \ud83e\udd13\ud83d\udcac<\/a><\/p>\n Stream\u2019s open-source chat and video SDK takes the complexity out of building real-time experiences. 100% free to start, extensible with popular integrations, and scalable!<\/p>\n Give it a try today<\/a>!<\/p>\n Issues with ScenePhase and using AppDelegate adaptors<\/a><\/p>\n At first glance, this is Jesse Squires<\/a> talking about exactly what the post title says, but this could equally be a post about API design trade-offs between flexibility and complexity. It appears that the SwiftUI interaction points during the application lifecycle are less granular by design.<\/p>\n Unobtrusive and testable issue reporting<\/a><\/p>\n I struggled to figure out the exact purpose of this new library from Brandon Williams<\/a> and Stephen Celis<\/a> at first glance until I read this line:<\/p>\n This provides a very visual way to see when an issue has occurred in your application without stopping the app\u2019s execution or interrupting your workflow.<\/p>\n<\/blockquote>\n I don\u2019t know if \u201cruntime warnings\u201d are new in Xcode 16 or whether I just haven\u2019t seen them before, but I like this idea.<\/p>\n Using @DebugDescription in Xcode 16<\/a><\/p>\n Here\u2019s Aryaman Sharda<\/a> with a write-up of the new @DebugDescription macro available with Xcode 16. I like that he also kindly includes another method to get similar results for those who can\u2019t yet upgrade to the beta.<\/p>\n Building Swift Executables<\/a><\/p>\n The only point I\u2019d add to Natan Rolnik<\/a>\u2019s post about building command-line tools is that adding a Makefile is a great way to manage build commands and other common scripts you might run. Makefiles may not be the newest technology, but they work very well and can serve as a \u201cmenu\u201d to show other developers what they can do with your repository.<\/p>\n A Paywall Optimization Success Story<\/a><\/p>\n The \u201cDay 5\u201d notification is essential to this paywall\u2019s design. I knew this would be the biggest technical and QA challenge, because it is imperative that it be implemented correctly. Failing to deliver on this promise would be catastrophic.<\/p>\n<\/blockquote>\n I can see why this style of free trial design works well. It\u2019s early days for Ryan Ashcraft<\/a>\u2019s implementation of it in his Foodnoms app<\/a>, but I can see it being successful.<\/p>\n macOS by Tutorials<\/a><\/p>\n I\u2019m so happy to see an updated second edition of Sarah Reichelt<\/a>\u2019s book covering macOS development. It remains a focused, concise book from the perspective of using SwiftUI first but falling back to AppKit where it makes sense. I\u2019m also happy that the story behind the second edition<\/a> ended so well. \ud83d\udc4d<\/p>\n For full disclosure, Sarah sent me a copy of the book for review.<\/p>\n Software Engineer for AI Training Data (Swift) @ G2i, Inc.<\/a> \u2013 We are currently seeking Swift Developers for project-specific roles focused on RLHF. This role will play a key part in our reinforcement learning from human feedback (RLHF) initiatives, contributing to cutting-edge projects. \u2013 Remote (within US, European, or Asia-Pacific timezones)<\/em><\/p>\n Software Engineer, iOS @ amo<\/a> \u2013 Amo values speed, creativity, and high performance. Focused on meaningful social apps, they prioritize creation over consumption and simple, fun experiences. The diverse, skilled team uses a modular monorepo tech stack with Rust, Bazel, and RxSwift, leveraging efficient data processing on GCP. \u2013 On-site (France)<\/em><\/p>\n Don\u2019t forget to post any open positions<\/a> you have available on iOS Dev Jobs<\/a>!<\/p>\n \u201cThey paid me sixty dollars, so I wore a tie<\/a>\u201d<\/p>\n<\/div>\n\n
Code<\/h2>\n
\n
Business and Marketing<\/h2>\n
\n
Books<\/h2>\n
Jobs<\/h2>\n
And finally…<\/h2>\n