The library brings native like swipe actions to ScrollView based lists (LazyVStack, Grid) where SwiftUI's native swipeActions do not work. Version 2.0 adds vertical swipe gestures from top and bottom edges, not just leading and trailing. It uses a familiar syntax (awesomeSwipeActions) with full UI customization via AwesomeSwipeButton or custom views. The AwesomeSwipeCoordinator keeps only one row open at a time and provides programmatic control (openRowID, close, open) for tutorials, async flows, or undo logic.
The article describes a horizontal ScrollView with cards of varying heights. The goal was to make all cards match the height of the tallest one. Using .frame(maxHeight: .infinity) alone caused each card to stretch to the full screen height because the HStack had no height constraint. The solution was adding .fixedSize(horizontal: false, vertical: true) to the HStack, which tells it to ignore the parent's height proposal and size itself to its ideal content height (the tallest card). The two modifiers work together: .fixedSize sets the correct container height, and .frame(maxHeight: .infinity) fills it.
The article explains Apple's Accelerate framework for high performance vectorized computation. It covers what Accelerate is (optimized APIs for vector math, matrix operations, signal processing, image processing, linear algebra, FFT, statistics), why it matters (naive loops miss SIMD hardware), the core philosophy (bulk computation instead of scalar iteration), major components (vDSP, vForce, BLAS, LAPACK, BNNS), practical examples (array addition, scalar multiplication, dot product, statistics, matrix multiplication with cblas_sgemm), performance considerations (Float vs Double, memory layout, benchmarking), common mistakes, and when to use or avoid it.
The article explains how to generate QR codes from text using Core Image's built in qrCodeGenerator filter. It presents QRCodeGenerator as an enum with static functions (acting as a namespace, not an initializable type). The implementation uses CIFilter.qrCodeGenerator(), sets the message as Data from the input string, applies error correction level M, scales the output image (typically by 12x because the raw output is tiny), converts to CGImage then UIImage then SwiftUI Image. The article also covers using .interpolation(.none) to keep edges crisp, separating user input from committed QR code text with two @State properties, and handling failure cases.
The article explains how to use the format parameter in Text and TextField to display and accept formatted values. It covers numbers (notation, grouping, sign, decimal precision), percentages, currencies, dates (date components, intervals, relative dates, ISO 8601), temperatures, distance, file size, concatenating collections with list style, person names using PersonNameComponents, and URLs (hiding scheme, path, or domain). It also shows the difference between interpolated strings and proper formatted numbers (locale awareness), and how TextField with format automatically drops invalid characters.
The article explains the three property wrappers for ObservableObject in SwiftUI. @StateObject creates and owns the instance, keeping it alive across view redraws. @ObservedObject is for passing an already owned instance to child views. @EnvironmentObject injects an object implicitly into a view hierarchy to avoid prop drilling. The article also covers the iOS 17 shift to the @Observable macro, which replaces @StateObject and @ObservedObject with @State, eliminates @Published, and enables granular dependency tracking (only views that read a specific property redraw when it changes).
This newsletter issue covers several iOS interview and coding topics. It explains how to answer an undo/redo system question with Core Data (basic undo manager, grouped operations, child contexts for multi-screen flows). It covers designing an Instagram style feed with clarifying questions (content types, ranking algorithm, interactions, offline support, page size, heterogeneous items). It includes a Swift Bite about task cancellation not stopping automatically (need to check Task.isCancelled or try Task.checkCancellation). It also has a hot take that SwiftUI is ready for production but teams may not be ready because they bring UIKit habits.

Join the Mobile Signal Talent Directory and make your profile visible to hiring teams searching for iOS talent.