iOSProgramming

Fatbobman's Swift Weekly #037 | Entering the Era of Futures

• Text Effects with TextRenderer
• onGeometryChange
• SwiftData vs Realm
• App Icon for iOS 18
• Translation Framework
• WWDC Sessions Guide

and more… #WWDC

At WWDC 2024, SwiftUI introduced the TextRender protocol, granting developers new powers to adjust the rendering performance of the Text component, making it possible to achieve many previously unimaginable effects. This article will delve into this new feature.

In this issue, I will share my personal insights of WWDC 2024 and compile a list of great articles on WWDC 2024's new features to help you understand each update in detail!

Fatbobman's Swift Weekly #035 | A Spectacular Keynote, Yet Practical Implementation Requires Time

• Dive into Swift 6, SwiftUI & UIKit’s latest from WWDC 2024
• Q&A of TCA
• Non-sendable Closure
• Core Image
• Transferable Protocol

Fatbobman's Swift Weekly #034 | WWDC 2024: AI is Not Everything

• SwiftData's Potential & Challenges
• AttributeGraph Insights
• Animating App Icons
• @preconcurrency Usage
• Scenes in SwiftUI
• WeatherKit Features
• Concurrency Migration Guide

Fatbobman's Swift Weekly #033｜Boosting Engagement: Forum Updates Alone Fall Short

• SwiftUI Changes
• Declarative Text Kit
• Build Website in Swift
• MVVM in SwiftUI
• Using TipKit
• Common Errors from UIKit to SwiftUI
• The Impact of AI Search Engines

Fatbobman's Swift Weekly #032｜Recognize the Importance of Accessibility Before It's Needed

• Swift Web Servers Performance
• Debugging Animations
• SwiftData Update Issue
• Selective Testing
• Strategies for Backend API
• Anticipation for WWDC

In SwiftUI, many layout container constructors include a spacing parameter with a default value of nil, which controls the spacing between adjacent views. This article will start with this default parameter to explore the concept of Spacing in SwiftUI in-depth, and share some related tips and considerations.

https://www.apple.com/newsroom/2024/05/apple-and-google-deliver-support-for-unwanted-tracking-alerts-in-ios-and-android/

https://www.privacymanifest.dev/

https://wemakeapps.net/manifest-maker

At the WWDC 2023, Apple introduced the containerRelativeFrame view modifier to SwiftUI. This modifier simplifies some layout operations that were previously difficult to achieve through conventional methods. This article will delve into the containerRelativeFrame modifier, covering its definition, layout rules, use cases, and relevant considerations. At the end of the article, we will also create a backward-compatible replica of containerRelativeFrame for older versions of SwiftUI, further enhancing our understanding of its functionalities.

In the toolbox of SwiftUI, overlay and background are two extremely useful view modifiers that play an indispensable role in various development scenarios. This article will delve into the unique attributes of these two modifiers, clarify their fundamental differences from ZStack, and identify the scenarios they are best suited for.

Apple recently updated its App Store Review Guidelines, now allowing emulator apps into the App Store. Just a few days ago, an emulator app named Delta was launched on the store. Delta is an all-in-one emulator designed for iOS, supporting a variety of Nintendo handheld games. This app was actually developed a long time ago but was previously only available to users in non-App Store formats due to policy restrictions.

SwiftData, as the successor to Core Data, has introduced a multitude of innovative and modern design ideas. Despite its availability for some time now, many developers have yet to adopt it in their projects. This situation is partly due to SwiftData’s higher requirements for the operating system version. Additionally, because SwiftData is not yet mature enough in some functionalities, developers might choose to continue using Core Data even if their operating system version meets SwiftData’s requirements. Can we integrate some of SwiftData’s excellent design philosophies and ingenious implementations into the practical use of Core Data? This article aims to explore how to introduce elegant and safe concurrency operations similar to those of SwiftData into Core Data, implementing a Core Data version of @ModelActor.

An increasing number of developers are starting to enable strict concurrency checks in preparation for the arrival of Swift 6. Among the warnings and errors received, a portion relates to SwiftUI views, many of which stem from developers not correctly understanding or using @MainActor. This article will discuss the meaning of @MainActor, as well as tips and considerations for applying @MainActor within SwiftUI views.

In the previous article Concurrent Programming in SwiftData, we delved into the innovative concurrent programming model proposed by SwiftData, including its principles, core operations, and related considerations. This elegant programming solution has earned considerable praise. However, as more developers attempt to use SwiftData in actual SwiftUI applications, they have encountered some challenges, especially after enabling Swift’s strict concurrency checks. They found that SwiftData’s actor-based concurrency model is difficult to integrate with traditional application construction methods. This article will explain, in a tutorial-like manner, how to integrate SwiftData with modern programming concepts smoothly into SwiftUI applications and provide strategies to address the current challenges faced by developers.

It’s another virtual conference year with an optional and free in person opening day. https://developer.apple.com/wwdc24/

I am planning on making an android app because I have a Google pixel 6 I got as a birthday gift and I love how open Android has gotten over the years.

I was wondering if it’s worth saving up to develop an iOS app. (The same app on Android, but for iOS) I know that the AppStore can be a good revenue spot for my app, not sure. My app will be free + Open Source Software, GPL (Version 3) of which I plan to add my own premium features or either a donation option for the privacy advocate folks.

I’ve had an iPhone 12 since 2021, and I’ve gotten used to our iOS works, how the system works in terms of iOS background and process’s.

One question;

> can I use GPL (version 3) for my iOS app on the AppStore?

I’m just want your thoughts if I should…

Thanks!

I’ve been working on this as a side project and would love to get some feedback on it :)

Features:

• Single Queue
• Follow YouTube feeds
• Triage videos
• Filter out #shorts
• Custom playback speed per channel
• (pre-select) chapters
• Picture-in-Picture
• … and some other stuff

The new business terms for iOS apps in the EU have three elements:

Reduced commission — iOS apps on the App Store will pay a reduced commission of either 10 percent (for the vast majority of developers, and subscriptions following their first year) or 17 percent on transactions for digital goods and services.

Payment processing fee — iOS apps on the App Store can use the App Store’s payment processing for an additional 3 percent fee. Developers can use a payment service provider within their app or link users to their website to process payments for no additional fee to Apple.

Core Technology Fee — iOS apps distributed from the App Store and/or an alternative app marketplace will pay €0.50 for each first annual install per year over a 1 million threshold.

Here are some tips to know so as to build accessible iOS apps in SwiftUI and UIKit, e.g. use of traits, notifications and zoom, with code samples.

Here are some tips about how you can make accessibility tests for your iOS apps with some screen shots and code samples

Orange group keeps alive and available an interesting and very rich web site providing plenty of rules and advices about accessibility. The content targets iOS, Android, web and also other mediums.

Kin is a minimalistic tool to check whether your project.pbxproj file is correct.

Kin is just a syntax checker built with ANTLR 4 with a very thin layer to be usable from command line.

Kin is helpful and under license Apache 2.0

I did something like this for analytics on the company app. It needs to record analytics to multiple providers for which a fan out pattern was a good fit. There's a single entry point to log an event. Any number of loggers then pick up that event and send it out to the provider. It has worked well and is even used for functionality inside of the app that should happen after a certain set of events occur in the app. For instance it prompts the user to rate and review the app after the user has performed a conversion event. A similar set of events will trigger the app to prompt the user to allow push notifications.

It's a nice explanation and exploration of how state in SwiftUI works.

> Apple introduced the new Observation framework powered by the macro feature of the Swift language. The new Observation framework, in combination with the Swift Concurrency features, allows us to replace the Combine framework that looks deprecated by Apple. This week, we will learn how to use the Observation framework to handle data flow in our apps.

I'm not sure that I buy the idea that Combine is deprecated. This does help reduce one use for it where it while increasing performance.

SwiftData by Example is the world's largest collection of SwiftData examples, tips, and techniques to help you build apps, solve problems, and understand how SwiftData really works.

> async/await in Swift was introduced with iOS 15, and I would guess that at this point you probably already know how to use it. But have you ever wondered how async/await works internally? Or maybe why it looks and behaves the way it does, or even why was it even introduced in the first place?

I've never been a big Core Data fan since it has cost me many days of my life debugging odd issues. To be fair, the issues weren't caused by Core Data. It was all of the foot-guns it left around that the junior developers on the team were more than happy to pick up and play with. This does look like an interesting use of macros though and is certainly a good example of how to craft more complex macros.

This is one feature that I missed from some other languages like Kotlin. It isn’t super useful for ifs but a switch with a lot of cases? Bring it on.