{"id":649,"date":"2025-01-01T20:21:00","date_gmt":"2025-01-01T19:21:00","guid":{"rendered":"https:\/\/www.paolorizzo.info\/?p=649"},"modified":"2026-06-30T13:21:17","modified_gmt":"2026-06-30T11:21:17","slug":"benvenuto-2025","status":"publish","type":"post","link":"https:\/\/www.paolorizzo.info\/en\/2025\/01\/01\/benvenuto-2025\/","title":{"rendered":"Welcome 2025"},"content":{"rendered":"

2024 has literally flown by. Months spent on training and the practical application of newly acquired knowledge.<\/p>\n\n\n\n

Skip.tools<\/strong>
It is the solution for iOS developers in situations that require producing applications for Android as well.<\/p>\n\n\n\n

Thanks to a framework and a few initial setup steps on your Mac, your Xcode application is simultaneously translated into Kotlin, making development and testing (almost) instantaneous: I can launch an Android emulator and see my app (natively written in Swift) running on both Android and iOS.
To learn more: https:\/\/skip.tools<\/a><\/p>\n\n\n\n\n\n\n\n

SwiftUI<\/strong>
I lived through the era of Objective-C and .Xib file-based UI design. After that phase\u2014which, with its manual memory allocation, was reminiscent of 1990s C\u2014I more than happily embraced Swift and its Storyboards. I followed SwiftUI without much enthusiasm at first, because visual (and imperative) programming seemed more immediate.
That is not the case: SwiftUI is a framework that redefines the approach to application UI, featuring methods that encapsulate and simplify interface creation and resource management.
Anyone who developed in the Apple ecosystem prior to 2019 knows just how much boilerplate code was required for tables, controllers, and views in general. SwiftUI streamlines development and reduces code volume, while offering superior portability compared to the old Auto Layout system.<\/p>\n\n\n\n

Swift Evolution (6.0 and beyond)<\/strong>
How many sleepless nights were spent debugging and wrestling with nightmares over asynchronous code riddled with closures and delegates? The arrival of async\/await and frameworks like Combine\u2014with its Publishers and Subscribers\u2014has made code much easier to understand, especially when dealing with nested closures.<\/p>\n\n\n\n

Welcome, AI<\/strong><\/p>\n\n\n\n

\u201cIf you can\u2019t beat them, join them\u201d\u2014that\u2019s what people used to say about the stronger party... but today, I prefer a mantra we should all repeat to ourselves every morning. <\/p>\n\n\n\n

“AI won't take your job,
but a designer who knows how to use AI to do work like yours\u201d<\/em><\/strong><\/p><\/blockquote><\/figure>\n\n\n\n

I\u2019ve studied the algorithms and tested a wide range of platforms as a user\u2014quickly building landing pages, dashboards connected to Firebase or Supabase (or, worse, databases built directly into the no-code platform), and even cross-platform apps, complete with images and video. I\u2019ve also followed various tutorials, including those where enthusiastic young creators\u2014with almost no technical background\u2014show you how to write code on a site, feed it into another portal to turn it into an app, and use yet another service to guide you through the publishing process.<\/p>\n\n\n\n

I have thoroughly explored every aspect of this area\u2014specifically regarding APIs and libraries that are not always readily available\u2014just as a developer wishing to implement these resources in their projects would need to do.<\/p>\n\n\n\n

There are two aspects to consider when enthusiastically embracing certain seemingly cheap offers:<\/p>\n\n\n\n