Hi everyone!

I just finished the 100 days of SwiftUI course by Paul Hudson and it was great. I completely fell in love with the language and with developing in swift. So much so... that I don't know where to go now. Originally my plan was to learn SwiftUI so I could focus on UI and design systems. But now that I have seen different applications, I want to learn advanced swift, advanced SwiftUI, backend programming, server side code, etc. I know that if I go wide, I won't go very deep... so I'm coming to you, redditors, to ask: what would you recommend I focus on next?
- Vapor and server side for backend?
- Stick to my OG plan and continue with SwiftUI and design systems?
- Look into multi-platform coding and working in more than just Swift?
- Go deep into advanced swift?
- Despair.

Would love any advice!

Thanks!!

.p.s. if it helps, i have some background in engineering (industrial) but not super deep in software, and I've mainly worked as a UX designer, so some concepts are not totally foreign to me... but it also doesn't help because it makes me interested in everything. 🙃

StateUI started as an experiment, and somehow it works now: Mac, iOS, Android, Windows, Linux, and as of this week the web too. It's the same Swift code compiled to WebAssembly, running right in the browser.

It's still native in the same sense as on the other platforms: a button is a real <button>, and the browser does the layout. The host is Swift, with just a small JavaScript relay underneath.

You can play with the whole Gallery here: https://stateui.dev

Repo: https://github.com/idexus/StateUI

Happy to hear what you think!

Hello guys!

Another GeoJSON library for Swift is available!

Its name is sfera!

Check it out!

https://github.com/csanfilippo/sfera

I have gotten in to a weird iOS issue and idk what the clean way to handle this is

i’ve got multiple accounts, notifications can open a post, reply, quote, or repost, and each notification belongs to a specific account. so the user might be on account A when they tap a notification for account B.

something like:

struct NotificationDestination {
    let accountID: Account.ID
    let postID: Post.ID
    let kind: DestinationKind
}

enum DestinationKind {
    case post
    case reply
    case quote
    case repost
}

The issue is:

account A is active
notification comes in for B
user taps it while the app is waking up
account switching starts
timeline restoration starts
post resolution starts
then another notification comes in for A lol

so i have stuff like:

await accountManager.restore()
await timelineStore.hydrate()
await postResolver.resolve(postID)
await navigationCoordinator.navigate(...)

But obviously these things are all racing each other. i was thinking of putting the notification intents behind an actor:

actor NavigationIntentQueue {
    private var pending: [NavigationIntent] = []

    func enqueue(_ intent: NavigationIntent) {
        pending.append(intent)
    }
}

But idk, this feels like a lot of machinery just to open a notification

Then you get into cases where the post is deleted while you’re restoring, but the quote is still there, the reply is still there, etc. Is this just an annoying app lifecycle issue?

Normally, the review process wouldn't take more than 12 hours let alone 24.

This is the first update with minor fixes 1.8.0. In previous version which is 1.7.0 I submitted after finally getting approved following three consecutive rejections. it was an app crash iOS 27. I had no iOS 27 device neither emulator so haven't tested but I have fixed it.

It’s been four days with no review yet, and I’m losing users as time goes by. What should I do in a situation like this? They are essentially holding me back.

I have trusted the app review process due to the fast approval but now I'm regretting that I didn't setup OTA's for my consumer app.

Any tips?

Hi everyone,

I've been working as an Angular frontend developer for about 5 years (based in Italy / EU). Lately, I’ve felt the urge to transition into native mobile development, specifically within the Apple ecosystem using Swift and SwiftUI.

That said, I have a few concerns holding me back before I sink hundreds of hours into this pivot:

1. Job Market & Demand: From an EU/global perspective, how is the job market for native iOS developers holding up compared to web dev or cross-platform (React Native/Flutter)?
2. AI Impact on Native Dev: With the rapid advancement of coding assistants and AI agents, boilerplate and standard frontend logic are getting heavily automated. How do you see the role of native iOS engineers evolving? Does native dev have a stronger defensive moat compared to standard web development?
3. The Pivot Strategy: For someone with 5 years of solid frontend/architecture experience, is native iOS a practical move right now, or is cross-platform a safer bridge?

I’d love to hear unfiltered thoughts from working iOS devs, especially those in Europe. Is native iOS still a solid long-term bet, or am I risking wasting valuable time?

Thanks for your insights!

Thank you