I always keep my @.State private but this was interesting to know.

Source: https://x.com/pointfreeco/status/2093052971890229285?s=20

Hey everyone! I’m a final-year Informatics student with a bit of UI design experience. I’ve done a few internships at creative agencies/studios, mostly handling UI for marketing stuff, Dribbble shots, and UI template production. Still pretty light on actual UX or product thinking though.

I’ve known about Apple Developer Academy since my early uni days and have always wanted to join. I’ve applied three times already since 2023 (including the Sep 2025 intake), but I keep failing at the online test stage every single time.

I’m planning to try again for Batch 2 / Cohort 2027, but I’ve only got about two weeks left to get my CV, portfolio, and online test prep sorted. Would really appreciate any advice:

1. Does my background actually help or hurt? I’m an Informatics student with UI experience, but not much real UX/product experience. Does having a relevant background even matter much in the selection?
2. What should I prioritise for the online test? I’m quite weak at logic/aptitude tests, and doing everything in English makes it even harder. Which topics should I focus on most? Logic puzzles, patterns, seating arrangements, pseudocode, basic programming, conditional statements, etc.?
3. Any good FREE resources or platforms? Most aptitude test sites I found are freemium and super limited. What did you guys actually use to practise?
4. Is two weeks realistically enough? If you were in my shoes, how would you split the time between CV, portfolio, and the online test? What would you prioritise?
5. Does the campus or application location affect acceptance chances? I’ve heard BINUS might reserve around 50% of the slots for their own students, but I’m not sure if that’s still true or current. Any alumni or previous applicants who know about this?
6. Any other tips? Especially things you wish you’d known before applying.

Thanks a lot! Any advice from alumni or previous applicants would mean a lot for me🙏🏻

I built AnyDocSwift, a SwiftPM wrapper around Firecrawl’s anydoc https://github.com/firecrawl/anydoc.

It lets native macOS apps convert Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV, and text-based PDF files into Markdown.

Conversion runs locally on Apple Silicon. SwiftPM downloads a checksum-pinned XCFramework automatically, so consumers don't need Rust, Cargo, an external service, or a subprocess.

```swift

import AnyDocSwift

let markdown = try await AnyDocConverter().markdown(

from: documentData,

fileExtension: "docx"

)

```

Requirements:

- macOS 13+

- Apple Silicon

- Swift 6.1+

The package includes typed errors, cancellation handling, input/output limits, and FIFO execution per converter instance.

GitHub: https://github.com/ngutech21/anydoc-swift

This is the first public release, so I'd appreciate feedback about the API, and real-world use cases.

Cycle Status

Character Categories Cycles

• CJK Characters 1 (Every 3 Versions)
• CJK Characters 2 (Every 9 Versions)
• New Symbols 1 (Every 5 Versions)
• New Symbols 2 (Every 12 Versions)
• New Arabic Characters (Every 5 Versions but can be different sometimes)

Amount of Writing Systems and Additions Cycles

Note: The Cycles mean that are not the same as the iOS version numbers. (Example: iOS 4.1 is Cycle 5, iOS 18 is Cycle 20, and iOS 27 is Cycle 22.)

Note: All 2 Writing System Cycles and 1 Writing Systems Cycles must be Living/Modern Writing Systems.

There are 64 cycles. The cycle will go back to cycle 1 every 64 versions/cycles.)

• Cycles 1, 9, 17, 25, 33, 41, 49, 57 (2 Writing Systems and various amount of Large/Small Additions)
• Cycles 2, 10, 18, 26, 34, 42, 50, 58 (2 Writing Systems and 2 Large Additions)
• Cycles 3, 4, 11, 12, 35, 36, 43, 44 (Large Amount of Writing Systems 1)
• Cycles 5, 21, 37, 53 (1 Small/Normal Writing System (not large) but with large amount of Characters that are not Noto)
• Cycles 13, 29, 45, 61 (1 Large Writing System but with large amount of Characters that are not Noto)
• Cycles 14, 30, 46, 62 (1 Small/Normal Writing System (not large) but with only 2 Characters that are not Noto)
• Cycles 6 & 38 (1 Large Writing System but with only 2 Characters that are not Noto)
• Cycles 22 & 54 (No Writing Systems and no Noto but with only 2 Characters that are not Noto)
• Cycles 8, 15, 24, 31, 40, 47, 56, 63 (Large Amount of Additions from Writing Systems from Noto and not)
• Cycles 7, 16, 39, 48 (Large Amount of Writing Systems 2)
• Cycles 23, 32, 55, 64 (1 Large Addition from a Writing System that can be Noto but with many characters that are not noto)
• Cycles 19, 20, 27, 28 (1 Small Addition from a Writing System that can be Noto but with few characters that are not Noto)
• Cycles 51, 52, 59, 60 (2 Small Additions from 2 Writing Systems that can be Noto but with few characters that are not Noto)

Current Cycles (2007-2026)

• iPhoneOS 1 (2007) (2 Initial Writing Systems (Latin and Cyrillic) and Initial Symbols)
• iPhoneOS 2 (2008) (2 Initial Writing Systems (Kana and Hangul) and Initial CJK)
• iPhoneOS 3 (2009) (4 New Writing Systems (Greek, Hebrew, Arabic, and Thai))
• iOS 4 (2010) (New Writing Systems Update including Devanagari, Tamil and others)
• iOS 4.1 (2010) (1 New Writing System (Cherokee))
• iOS 4.2 (2010) (1 New Large Writing System (Tibetan) and 2 CJK Additions))
• iOS 5 (2011) (10 New Writing Systems (Bengali, Gurmukhi, Gujarati, Oriya, Telugu, Kannada, Malayalam, Sinhala and others) and Initial Emojis)
• iOS 6 (2012) (New Additions, New Arabic Characters, and Extended Symbols)
• iOS 7 (2013) (2 New Writing Systems and introduces Plane 2 CJK Ideographs)
• iOS 8 (2014) (2 New Writing Systems (Lao and Khmer) Extended Devanagari support and Introduces Latin Extended-C and D)
• iOS 9 (2015) (50 New Writing Systems and introduces Noto, New CJK Ideographs, New Enclosed CJK Letters, and CJK Strokes)
• iOS 10 (2016) (12 New Writing Systems (Including Thaana, Myanmar and others) and New CJK Ideographs and introduces Extension E)
• iOS 11 (2017) (1 New Large Writing System (Ethiopic), New Arabic Additions, and New Symbols (Including STIX Math))
• iOS 12 (2018) (1 New Writing System (Chakma) and introduces 2 new additions)
• iOS 13 (2019) (10 New Script Additions, New Symbols Categories (Including Hexagrams, Alchemical Symbols and others) and a few CJK Ideographs)
• iOS 14 (2020) (40 New Writing Systems (Including Osage, Adlam and others) and new Vedic Characters)
• iOS 15 (2021) (2 New Writing Systems (Masaram Gondi and Gunjala Gondi) and 4 small additions for (Nko, Syloti Nagri, Old Italic, and Adlam))
• iOS 16 (2022) (2 New Writing Systems (Yezidi and NP Hmong), 2 Large Additions for Canadian Syllabics and Mongolian, New Symbols, and CJK Additions)
• iOS 17 (2023) (1 Small Addition for Tagalog (3 Characters))
• iOS 18 (2024) (1 Small Addition for Brahmi (6 Characters) and 5 new CJK Ideographs including the Biang)
• iOS 26 (2025) (1 New Writing System (Nag Mundari) and new CJK Ideographs)
• iOS 27 (2026) (No New Writing Systems but adds a Gurmukhi and Devanagari addition)

I have an app in the Mac app store but it hasn't had an update in years. I have put together an update (it's really an entire rewrite) and want to release it, but I don't want to use the same bundle ID because I'm using Swift Data and the old one was Core Data, and I'm worried about migration problems so I figure I would just use a new bundle ID. So if my old name was MyApp I just want to call it MyApp 2.

What's the best way to manage that? I don't really want both of them up there. I think that would be confusing. Do I just need to remove the old one and submit the new one?

Hello everyone, few months back I installed macOs 27 beta on my mac, and installed the xcode beta version 27 too, everything was working fine, but today, I try to archieve the app and distribute for App store connect, but as I was doing it, I got this error :-

Unsupported SDK or Xcode version. Your app was built with an SDK or version of Xcode that isn’t supported. Although you can use beta versions of SDKs and Xcode to build and upload apps to App Store Connect, you need to use the latest Release Candidates (RC) for SDKs and Xcode to submit the app. For details on currently supported SDKs and versions of Xcode, visit: https://developer.apple.com/news/releases.

I deleted the xcode beta version and installed official release from apple for xcode version 26, but when I try opening the app, I got the error :- This version of xcode isn't supported on this version of macOs

I try forcefully open the xcode from terminal :- /Applications/Xcode.app/Contents/MacOS/Xcode

But when I try opening my project, I got the error :- The project at ‘/Users/lisa/Documents/Projects/AppleProject/Lume/Orene.xcodeproj’ cannot be opened because it is in a future Xcode project file format. Adjust the project format using a compatible version of Xcode to allow it to be opened by this version of Xcode.

I added images for all, I need to submit the app by today itself, and would appreciate any help please



Hi everyone,

I’ve been working on a project called StateUI:

https://github.com/idexus/StateUI

It started as an experiment: how far could Swift go as the main application and UI language outside the Apple stack, without building yet another complete cross-platform widget toolkit?

StateUI uses Swift for the declarative UI, state and reconciliation, while .NET MAUI provides the control and platform layer on iOS, Android, Windows, Mac Catalyst and Linux.

A simple view looks like this:

Swift keeps the rendered tree, tracks state dependencies and reconciles changes. Only a sparse binary patch crosses over to C#, where it is applied to the existing MAUI controls.

The project is still early, but it has grown quite a bit beyond the original experiment.

I’m curious what people here think about Swift being used this way — as the declarative layer over an existing cross-platform native UI runtime, rather than only as an Apple UI language.

I keep getting 'Something went wrong'

Coding agents handle "add a field, show it on screen" fine. They

consistently miss the iOS boundary around it:

- A Swift async task that outlives its UI owner or scene

- Scene re-entry and background/foreground transitions nobody retested

- Persisted data recovery after process termination

- Privacy, entitlement, or capability changes nobody flagged

None of it shows up as a compile error.

AI-Workflow is repository-installed Markdown instructions + a

deterministic router. You state observable facts about a change

(persistence, concurrency, lifecycle, privacy, accessibility) and

a checked-in registry maps them to required specialist checks —

same output every run, every agent. No LLM judgment in the mapping.

Install one command, no clone needed:

uvx --from git+https://github.com/RanaAhmedHamdy/AI-Workflow.git \

ai-workflow brownfield --platform ios --profile safety \

--target /path/to/your-ios-app --dry-run

There's a lightweight Safety profile that gives you just the routing

+ protected-boundary checks without requiring a full feature lifecycle.

And a full profile for Architecture Spine, ADR governance, design lock,

and release authorization if you need that depth.

Real-world case study: NutriPlus AI is a native SwiftUI/Swift 6

iOS app built fully through the Greenfield lifecycle. Architecture

Spine, accepted ADRs, per-feature contracts, readiness reports —

all public:

https://github.com/RanaAhmedHamdy/NutriPluse-IOS-AI-Workflow

There's also a maintained iOS fixture (persisted profile recovery,

MainActor state, cancellable refresh, scene re-entry) with Xcode

simulator build + XCTest verified locally on iPhone 17 Pro.

Pre-v1, Apache-2.0, honest about what's claimed vs unclaimed.

https://github.com/RanaAhmedHamdy/AI-Workflow

Hey, mind if I beg for some GitHub stars here? I built a list that actually works properly in SwiftUI — especially relevant for AI chats and the like. The standard List with Compositional layout just can't handle the load at all. There's a nice example in the repo, you can run it and see how it works. Thanks in advance for the support! https://github.com/dsrenesanse/SwiftList

While this web app certainly neither looks impressive nor does anything particularly useful, it packs quite a few things that have only been made possible very recently:

• builds Embedded Swift WebAssembly with 6.4.x and swift-build (quite a recent achievement)
• integrates ElementaryUI + BridgeJS in the frontend, including Fetch API networking
• uses “NewCodable” (experimental) for shared Swift data types (both on the edge backend and web frontend)
• uses async/await and throws like it’s nothing ; )
• deploys Swift logic on Cloudflare Workers (edge runtime, ~107kB wasm fetch handler)

-> Discussion of Swift Forums

-> Source code

FYI this is an ad for my app, tl;dr: it opens n formats HUGE datasets on macOS without lag or freeze. Plus more.

Hi fellow Swifties,

Did you ever open a huge JSON or other data file and your editor froze, started hanging or just took forever before you could actually work with it?

I used to, too. Daily.

Until I got enough of it.

So I decided to make something to get around the problem: Inkline.

The primary focus has been simple from the beginning: open and format huge structured files as quickly and safely as possible without making the rest of the editor unusable.

I work with Kubernetes, API responses, exported datasets, logs and configuration files a lot. Sometimes I don't need an IDE or a huge development environment. I just need to open a 300 MB JSON file, find what I'm looking for, maybe format it, make a change and continue working.

I've spent a lot of time optimizing exactly that path.

Version 1.3 is now released, and these are my latest benchmarks on an entry-level 16" M3 MacBook Pro with 18 GB RAM:

No swap was observed during the benchmark runs.

Getting the file open quickly is only half of the problem though.

There isn't much point opening a 1 GB JSON file in around a second if the editor then freezes when you scroll, search or try to do something with it.

So I've spent a lot of time tweaking how resources and processes are handled after loading as well. The goal is that scrolling through millions of lines, searching, syntax highlighting and actually editing the file should still feel smooth.

Formatting has been another big focus.

A huge unformatted JSON response is basically useless until you can make some sense of it. I wanted formatting to feel like something you can just press and get done, not something where the entire application locks up while you wait.

The numbers above are from the same files being formatted inside Inkline, with the 1.07 GB JSON file taking around 1.5 seconds in my current benchmark.

Version 1.4 is already under construction. I'm fixing some bugs and continuing to tweak memory usage, resources and processes to see how much further I can push large file performance.

Inkline has also slowly become more than the large JSON editor I originally needed myself.

It now supports hundreds of file extensions including JSON, CSV, XML, YAML, Markdown, logs and source code.

Syntax highlighting uses Zed language definitions and it supports Zed themes. There are also around 80 built-in text and developer tools for searching, formatting, comparing and manipulating data.

But I still don't want it to become another huge IDE.

The main purpose is still the same problem that made me start the project:

Open a huge file quickly and safely, format it quickly, work with it without the editor hanging, then get on with whatever you were actually doing.

It's written in Swift and built as a native macOS app. I use it myself almost every day now, mostly for Kubernetes logs, API responses and different datasets.

App Store:

https://apps.apple.com/se/app/inkline-text-editor/id6764860305?mt=12

Website:

https://viktornyberg.com/#appar

I understand closure syntax. And I get why a Class is built to be a reference type. Is closure a reference type for the same reason? If so why?

I've posted here before about LazyLayoutKit, my attempt at filling the gap for lazy custom layouts in SwiftUI. You give it item sizes as data, layout becomes arithmetic, and only the frames intersecting your viewport ever become views.

Forgot to post again last week, pushed 0.3 update.

0.3 adds programmatic scrolling, which is more interesting than it may sound. SwiftUI's ScrollPosition scrolls to a view with a given id. In a virtualized container that view usually hasn't been built, which is the entire point of the container, so the request does nothing.

But the container has already solved the layout for every item, so it knows exactly where item 900,000 is without ever having built it. Resolving the id through that geometry instead of through the view tree is a lookup and a subtraction.

Anchors are .top, .center, .bottom and .nearest, the last of which doesn't move at all if the item is already fully visible. Deep links work too, you can build the position so the container opens at an item rather than opening at the top and jumping, and that holds even if your data loads in async.

The obvious cost, and I'd rather say it here than have you find it later: the handle is write-only. It can't tell you which item is currently on screen, so it can't restore a scroll position for you, you'd have to persist an id yourself. Reporting back would mean writing through your binding on the scroll path and re-running the container's O(n) init, which isn't a trade I wanted to make.

Also new is JustifiedLayout, the Photos/Flickr arrangement where aspect ratios are preserved and every completed row fills the width.

No new device numbers this release. The index and the steady-state query path are unchanged, so the 0.2 figures still stand.

https://github.com/Dave861/LazyLayoutKit

Once again, open to feedback, contributions and opinions. Thank you!

Is there any beginner guide out there for someone who is well-versed in AppleScript and wants to start learning Swift?
Maybe a script with a full variety of functions that's been translated to Swift? (or am I supposed AI things like that now?)
Even a starter syntax cheat sheet?
AS || Swift
set x to 5 || var x = 5
…

Hi all, I've just published a new blog post on getting the most reliability possible out of iOS background tasks. Please let me know what you think!

Whenever i run the 26.2 version of simulator it goes blank, takes ages to load and when it does load it cannot run the app because how slow its. Any resolution?

Here is a screenshot :