\n<\/p>\n
The most interesting article I read this week was Abdallah W Shaban<\/a>\u2019s post on the official Flutter blog, \u201cRich and dynamic user interfaces with Flutter and generative UI<\/a>\u201d.<\/p>\n Yes, it\u2019s about a Flutter package, GenUI<\/a>, but it was the idea that caught my attention. It takes the idea of using LLMs inside an app one step further than having the model return text or structured data. Instead, it returns UI widgets that also contain the LLM-generated content! In the demo video<\/a>, Andrew Brogdon<\/a> uses the example of building a chat-style interface for a workout app, but that\u2019s far from all it can do. I\u2019d recommend watching this 30-second slice<\/a> of the video for a better explanation than I can manage in a few words.<\/p>\n I\u2019d imagine that using LLMs to generate free-form UI for data would be possible using the most cutting-edge models, but it\u2019s not something I\u2019d want to ship without more structure, and that\u2019s what GenUI is doing. It includes a built-in set of widgets for common UI, and you can add your own too. As I understand it, the package iteratively processes the LLM response, selecting the most appropriate widget from its library for each piece of content until the entire response has been rendered into UI. Perfect for a conversation-style UI, as demoed, but also for homepages or anywhere else you want to display a dynamic set of information to your user.<\/p>\n I expect the current set of online models to be extremely capable of picking the best widget from a finite set, and the concept is a natural step forward from generating typed data objects. Would it be possible using Apple\u2019s local foundation model? It can already generate typed data, and could probably take a small set of UI descriptions in a prompt and include the best fit in its response. I think it\u2019d be worth playing around with if any of you fancy a weekend experiment. I\u2019d love to hear where you get to if you give it a try, especially if you have a use-case in a real app.<\/p>\n I\u2019m heading out on a much-needed holiday for the next couple of weeks, so there will be no issues for the next three weeks<\/em>! \ud83d\ude31 I\u2019ll be back on the 19th of December! See you all then.<\/p>\n \u2013 Dave Verwer<\/p>\n Cut Code Review Time and Bugs in Half<\/a><\/p>\n Code reviews are critical but time-consuming. CodeRabbit<\/a> reviews every pull request instantly, providing detailed comments, fix suggestions, and impact analysis. You can even define custom code quality rules with AST Grep patterns to catch nuanced issues that static tools miss. Already trusted across 2M+ repositories and 100K open-source projects. Get started today<\/a>.<\/p>\n Embedded Swift Improvements Coming in Swift 6.3<\/a><\/p>\n First, Android<\/a>, and now Embedded! Swift 6.3 is going to be a significant release for non-Apple platforms. It has been possible to get Swift apps running on really tiny devices for a while now (as mentioned in Issue 655<\/a>, Issue 673<\/a>, and Issue 691<\/a>), although getting it going was not trivial. Having embedded as part of nightly builds, and eventually of the stable Swift release, is a huge step forward.<\/p>\n Swift projects in the 2025 Google Summer of Code<\/a><\/p>\n It\u2019s been a great Google Summer of Code for Swift this year with Priyambada Roul adding Swiftly support to VS Code<\/a>, Ahmed Elrefaey improving Swift\u2019s code completion<\/a>, Mads Odgaard extending swift-java interoperability<\/a>, and Tien Quoc Bui improving console output for Swift Testing<\/a>. I love that the Swift team supports this initiative so well, and of course, it goes without saying that I\u2019m grateful for all the work that the participants and mentors put into this year\u2019s projects.<\/p>\n Visual debugging with Swift Charts<\/a><\/p>\n Dimi Chakarov<\/a>:<\/p>\n When I decided to implement the algorithm Soroush Khanlou<\/a> so brilliantly described in his Elevated Swift talk<\/a> I didn\u2019t expect that the hardest part would be not the algorithm for the elevator (or lift, as we call it here<\/a>), but rather the one for generating the traffic.<\/p>\n<\/blockquote>\n Soroush Khanlou<\/a>\u2019s conference talk from Swiftable 2022<\/a> in Buenos Aires is worth a watch, and the chart-led approach to problem-solving in the post is interesting, too.<\/p>\n Attach to Multiple Processes<\/a><\/p>\n Daniel Jalkut<\/a>\u2019s latest post isn\u2019t going to be immediately useful for everyone, but I found it interesting, and it set me thinking. Maybe you\u2019ll find it interesting or useful, too!<\/p>\n Handling Non-Breaking Numbers in Dynamic Text<\/a><\/p>\n This tip from Artem Mirzabekian<\/a>\u2019s latest post won\u2019t be news to you if you\u2019ve ever done front-end web work, but the technique is just as useful in native frameworks!<\/p>\n Indie, Alone, and Figuring It Out<\/a><\/p>\n Danijela Vrzan<\/a>:<\/p>\n Going indie is exciting. Total freedom, no 9\u20135, no meetings – just building your own app. I imagined quiet mornings, deep focus, full control over my day. And some of that is true. But once you\u2019re actually doing it, you discover a whole other side of indie life.<\/p>\n<\/blockquote>\n If you\u2019re already independent, you\u2019ll nod along with every word. If you\u2019re thinking about making the leap, Danijela\u2019s post should be required reading before you take the plunge.<\/p>\n When To Kill A Project<\/a><\/p>\n I don\u2019t usually link to articles about me, but I thought this one came out quite well. When Jacob Bartlett<\/a> asked me to contribute to his \u201cWar Stories\u201d series, I suggested we chat about a few failed projects that I have attempted over the years, as the best advice can come from other people\u2019s failures! \ud83d\ude2c<\/p>\n Videos from ServerSide.swift 2025<\/a><\/p>\n I wrote about ServerSide.swift 2025<\/a> back in Issue 729<\/a>, but if you missed the conference, you can at least now catch up with the session videos!<\/p>\nNews<\/h2>\n
Code<\/h2>\n
\n
Business and Marketing<\/h2>\n
\n
Videos<\/h2>\n
And finally…<\/h2>\n