





















































MobilePro #165: Introducing Swiftly, what's new in Swift 6.1, GPT-4o, WWDC 2025, and more…
Hi ,
Welcome to the 165th edition of MobilePro! We hope you are having an exciting week and are ready to explore the world of mobile development. From a flurry of announcements in the world of Swift, with both Swift 6.1 and Swiftly 1.0 being released, to WWDC 2025’s upcoming in-person event and Google’s major shift in Android development—there’s a lot to unpack:
🎨 OpenAI rolls out native image generation in GPT-4o to free users with conversational refinement, alongside upgrades to speech models for more dynamic voice interactions.
💻 Swift 6.1 is now available. This release includes updates to the language and package manager as well as details on how to get started with this new version, especially with the release of Swiftly 1.0 (as detailed up next).
🛠️ Meet Swiftly 1.0 – the new way to manage Swift versions, now a significant part of the core Swift toolchain and soon to become the default way to install Swift outside of Xcode.
🍏 WWDC 2025 is coming up on June 9 and applications are open until April 2 (11:59 p.m. PT). Don’t miss your chance to be part of this exciting in-person event at Apple Park for developers!
📱 Google is taking Android development behind closed doors, moving away from AOSP to streamline its processes. Get all the details on what this means for the future of Android.
That isn’t all. Just like in the previous edition, the What's Happening in AI? section will glance at all the developments in the world of artificial intelligence, including a look at how the Studio Ghibli trend overwhelmed OpenAI. We also have the Developer Tip section to enhance your workflow and the Did You Know? section, because how else can you plan for the future without knowing your past?
Let’s dive in!
P.S.: If you have any suggestions or feedback, or would like us to feature your project on a particular subject, please write to us. Just respond to this email!
If there’s any major news in the world of mobile app dev in the last week, MobilePro has you covered.
What are mobile app developers discussing? Do you have any concerns, advice, or tutorials to share? MobilePro brings them to you all in one place.
AI is evolving fast—are you keeping up? MobilePro brings you key discussions, trends, and expert takes in one place.
MobilePro presents the latest titles from Packt that ought to be useful for mobile developers.
Designing Information Architecture is your guide to building intuitive digital spaces, helping users navigate information overload with ease. Written by UX expert Pabini Gabriel-Petit, it covers proven IA design strategies, effective search systems, and modern AI-driven approaches. Whether you're structuring websites, apps, or intranets, this book offers practical insights to improve organization, findability, and usability.
SwiftUI, like any other framework, can have its own quirks. For instance, why does @viewbuilder allow just 10 views and not more?Michele Fadda's An iOS Developer's Guide to SwiftUI is here to help you out on that front, with the following excerpt:
In this section, we will explain why we have a limit of just 10 child views, for example, on HStacks and VStacks.
The @SwiftUiBuilder attribute is a result builder that allows the creation of child views for a SwiftUI view without the need for return keywords.
You are already using @ViewBuilder; internally, the definition of the protocol View internal to the SwiftUI framework is the following:
Public protocol View {
Associatedtype Body:View
@ViewBuilder var body: Self.Body { get }
}
There is no need to add the preceding code yourself, as this is a part of the SwiftUI code.
The effect of this protocol declaration is that you can write your SwiftUI body the way you have seen so far, that is, omitting the return. Take the following example:
struct ContentView: View {
var body: some View {
Text("Example")
}
}
@ViewBuilder is defined this way inside SwiftUI:
@available(iOS 13.0, OSX 10.15, tvOS 13.0, watchOS 6.0, *)
extension ViewBuilder {
public static func buildBlock<C0, C1>(_ c0: C0, _ c1: C1) -> TupleView<(C0, C1)> where C0 : View, C1 : View
}
@ViewBuilder contains a static buildBlock method that receives two views and returns a TupleView function of generic views conforming to the View protocol.
@ViewBuilder also has similar definitions for up to 10 different views.
This is the underlying reason why @Stackbuilder and the views built with it, for example, HStacks and VStacks, can only contain up to exactly 10 different views.
We can use @ViewBuilder directly ourselves, inside initializers, definitions of methods, or in front of properties.
By using the @Stackbuilder result builder, it is possible to create more compact code and improve readability, or we can create our version of a view, kind of like a custom UI component.
***
Read Michele Fadda’s further thoughts and work in An iOS Developer's Guide to SwiftUIto find out.
If you’re a React Native user, this one’s especially for you. Priya Bapodra, a software engineer in the mobile dev space, has listed out 7 tips that will help you while navigating React Native. Here's one of those tips:
"While inline styles are easy to use, they can be less efficient and harder to manage in larger projects. Opt for StyleSheet.create to improve performance and make styles more maintainable."
You can read the remaining tips in Priya’s LinkedIn post here.
In case you have any tips to share with your fellow mobile developers, do reply to this mail and we’d be glad to feature you in a future edition of MobilePro.
On April 3, 1973, the first-ever mobile phone call creates history. Standing on Sixth Avenue in New York City, Motorola engineer Martin Cooper made a call that reshaped communication forever. Using the Motorola DynaTAC—a 2.5-pound, 10-inch prototype—he dialed his rival, Joel Engel of Bell Labs, proving that mobile phones weren’t just a concept. That moment kicked off the shift from bulky, stationary phones to the pocket-sized essentials we rely on today.
Sourced from Android Authority.
👋 And that’s a wrap. We hope you enjoyed this edition of MobilePro. If you have any suggestions and feedback, or would just like to say hi to us, please write to us. Just respond to this email!
Cheers,
Runcil Rebello,
Editor-in-Chief, MobilePro