\n<\/p>\n
Watching this video<\/a> from Daniel Leivers demonstrating his master\u2019s dissertation this week set me thinking.<\/p>\n What Daniel has built is clearly impressive. You can sketch UI with your iPad\u2019s pencil and see real interactive UI or Swift code appear alongside it. The app uses a model created from sketched UI components fed into the yolov5<\/a> algorithm and converted to a CoreML model to generate code from the identified UI components. It\u2019s a good idea and makes a fantastic demo. If you\u2019re interested in reading his dissertation, it\u2019s available here<\/a>.<\/p>\n I took a couple of things away from Daniel\u2019s video. With all the light shining on GPT and LLMs at the moment, it\u2019s easy to forget that CoreML is still capable of building amazing features like this. It\u2019s also easy to think that AI means \u201crunning in the cloud\u201d with how resource-intensive LLMs are, but this all runs locally.<\/p>\n But more significantly, his video set me thinking about progress. Thinking back to my own final year project that made up part of my software engineering degree that I completed in 1996, 28 years ago. I created an HTML editor using Borland Delphi 1<\/a>. Remembering what my app did, it seems almost comical. It did not have an integrated browser preview, syntax highlighting, auto-completion, auto-indentation, or any number of other features that would be table stakes for even the most basic code editor today. To give you an idea, it was a slightly less capable version of something like this<\/a>. I was still proud to complete it, though, as I am sure Daniel is proud of his project.<\/p>\n But still, I stood on the shoulders of giants to create my little 16-bit text editor, and so did Daniel with his remarkable iPad app. There are obvious dependencies like the machine learning algorithms and CoreML, but there are so many more that you might not immediately consider. Think about some of the more \u201cmundane\u201d parts of his app. How difficult would it have been to implement the sketching functionality without PencilKit? Not to mention technologies like SwiftUI, UIKit, the Swift language, Foundation, and even Darwin!<\/p>\n I don\u2019t say this to undermine the amount of work Daniel did on his project. I want to celebrate<\/em> the amazing technologies and development environments we have access to today that make projects like this possible as dissertations.<\/p>\n We truly do stand on the shoulders of giants I stood on the shoulders of the giants that created Borland Delphi, HTML, and the web back in 1994 and Daniel stands on countless researchers and computer scientists that made his project possible. One of the things I love about this industry is that even if we build an app in a team of one, we\u2019re not working alone. Whether open or closed source, the APIs that others create are constantly pushing the industry forward and it\u2019s a huge part of why it\u2019s one of the fastest-paced industries that exist. I find it incredibly inspiring.<\/p>\n \u2013 Dave Verwer<\/p>\n Nail the toughest tech interviews<\/a><\/p>\n Get trained by tier-1 instructors with individualized coaching and 1:1 sessions, mock interviews, and personal feedback. Register now<\/a> for the next Interview Kickstart webinar and nail your next interview.<\/p>\n Provide your trader status in App Store Connect<\/a><\/p>\n You probably received an email yesterday telling you to add your \u201ctrader status\u201d to App Store Connect. The legal definition of a trader is hard to parse, but I think RevenueCat\u2019s attempted definition<\/a> is reasonable:<\/p>\n If you make money with your app, probably.<\/p>\n<\/blockquote>\n Many people are upset about needing to provide an address and phone number that will be public, but don\u2019t think it\u2019s unreasonable. Maybe it\u2019s because I\u2019m used to needing to have a public business address in the UK, but I don\u2019t have a problem with the EU requiring businesses not to be anonymous. If you\u2019re on an individual account, it\u2019s trickier, but if you\u2019re making money then you might be about to cross that line to becoming a business. There are good tips on avoiding exposing your personal address in the RevenueCat article<\/a> for those based in the US, so I\u2019d recommend reading that.<\/p>\n Note:<\/strong> RevenueCat are a sponsor of this newsletter, but I am including this link here not as part of any sponsorship, but as it contained by far the clearest explanation I found about all this.<\/p>\n Visual Studio App Center Retirement<\/a><\/p>\n I\u2019m sad to see the retirement of Microsoft\u2019s App Center as it means the end of the timeline for HockeyApp<\/a>, which was always my favourite way to distribute apps for testing before Apple released their integration of the competing TestFlight service\u00b9. The retirement makes perfect sense, of course, since both Apple and Google have fantastic pre-release distribution systems, and Microsoft gives details of other services that people can use for the other pieces of functionality it had. I was sceptical but also hopeful<\/a> when the acquisition happened, but it turned out much better than expected. I doubt many of you were using App Center in 2024, but I link to this announcement mainly because I want to give one more link to HockeyApp. \ud83e\udee1<\/p>\n \u00b9 One of the rare occurrences where Apple purchased a company and didn\u2019t<\/em> rebrand it. There are others, like Siri, Beats, and Shazam, but they are few and far between.<\/p>\n How to link to native type extensions in DocC<\/a><\/p>\n Daniel Saidi<\/a> on DocC in Xcode 15:<\/p>\n While DocC was already great, Xcode 15 made it even better. You can now use metadata to describe your pages, create interactive tabs and grids, and much more.<\/p>\n<\/blockquote>\n He goes on to explain one of the biggest features in this year\u2019s DocC release, support for documenting your extension methods.<\/p>\n Nerdy internals of an Apple text editor<\/a><\/p>\n I enjoyed Mihhail Lapushkin<\/a>\u2019s write-up on creating a Sending trial notifications with provisional authorization on iOS<\/a><\/p>\n As Natalia Panferova<\/a> explains in this article, \u201cprovisional\u201d push notifications are a powerful way to show your users that your app can provide useful information via push before without needing any opt-in from users at all. This doesn\u2019t use a new API, it was introduced with iOS 12, but I don\u2019t see enough apps taking advantage of it.<\/p>\n Complementing Unit Tests with Performance Checks<\/a><\/p>\n We\u2019ve all probably run some kind of benchmark against a piece of code we\u2019ve written at some point, but I bet most of them get thrown away once we reach the point of \u201cYep, it\u2019s good enough!\u201d<\/p>\n How about if we made that benchmark a part of our test suite, so we know if it regresses? Joakim Hassila<\/a> believes that would be a good idea, and made a package<\/a> to make it easier!<\/p>\n Guide to Naming SwiftUI Components<\/a><\/p>\n This is a great tip on naming SwiftUI components, and a great example that not all blog posts need to be epic! Useful is useful. \ud83d\udc4d<\/p>\n iOS Engineer @ trivago<\/a> \u2013 trivago, a metasearch engine using real-time auction and petabytes of data, enables millions of travelers compare hotel prices from hundreds of booking sites. Based in D\u00fcsseldorf, we foster a culture of learning and innovation, embracing flexibility for our talents to shape the travel industry. \u2013 On-site (Germany) with some remote work (Anywhere)<\/em><\/p>\n Senior iOS\/macOS Developer @ Paste<\/a> \u2013 Joining Paste means crafting impactful, user-focused products alongside a team that values innovation, flexibility, and a culture of collaboration. Dive into projects that push the boundaries, enjoy freedom in how you work, and help shape the future of productivity tools. \u2013 Remote (within European timezones)<\/em><\/p>\n If you\u2019d like to see your job featured in iOS Dev Weekly, post it on iOS Dev Jobs<\/a> and select \u201cFeatured listing\u201d as you check out, and it\u2019ll be in next week\u2019s newsletter. \ud83c\udf89<\/p>\nNews<\/h2>\n
\n
\n
Code<\/h2>\n
TextView<\/code>-based editor. He tackles lots of background and high-level details in his first article<\/a> and moves to the technical side of things in the second part<\/a>. Both are very well-written and illustrated, and I\u2019d recommend checking them out!<\/p>\nJobs<\/h2>\n
And finally…<\/h2>\n