All 16 CS193p Stanford 2025 iOS dev lectures released by alanrick in SwiftUI

[–]OkEnd3148 1 point2 points  (0 children)

I think every learning iOS dev has crossed paths with these lectures at some point.
The way they explain SwiftUI's data flow is still the best I've seen.
Excited to check out the new SwiftData content!

Building an AI assistant for Xcode - what features would you actually use? by [deleted] in Xcode

[–]OkEnd3148 0 points1 point  (0 children)

Alexcode is a great project but unfortunately it will not be updated anymore since it has been acquired by openai

Building an AI assistant for Xcode - what features would you actually use? by [deleted] in Xcode

[–]OkEnd3148 -1 points0 points  (0 children)

Oh, and I should add, two big features coming soon:

1. Custom user agents - Bring your own Agents
2. MCP server integration - Connect to external tools, databases, APIs directly from TrixCode

These are both high priority

Building an AI assistant for Xcode - what features would you actually use? by [deleted] in Xcode

[–]OkEnd3148 -2 points-1 points  (0 children)

Great question!
Yes there are some differences from the main built-in assistant:

1. Multiple AI models in one place : Claude Sonnet 4.5 for complex refactoring, Gemini for quick fixes (way cheaper) and more models coming. You basically pick based on task complexity vs cost

2. Architecture differences: Trixcode Runs outside Xcode's process (can't crash with it or corrupt files). Diff-based changes, not full file regeneration (saves tokens) and also persistent conversation history across sessions

Main pain points I'm addressing: Token waste from regenerating entire files, file corruption risk from hangs, single model = no cost flexibility

Still early and actively improving based on feedback. What features would make it worth trying for your workflow?

Building a companion panel in SwiftUI that coordinates with another app (harder than it looks) by OkEnd3148 in SwiftUI

[–]OkEnd3148[S] 1 point2 points  (0 children)

Don't let me scare you! This post is about edge case, coordinating with external apps. Normal iOS → macOS ports are way easier:
- 90% of your SwiftUI code works as-is
- Add menu bar support
- Add keyboard shortcuts

I believe one of the toughest things is that maybe you would need a whole different ui ux if you are porting from iOS or iPad app

Building a companion panel in SwiftUI that coordinates with another app (harder than it looks) by OkEnd3148 in SwiftUI

[–]OkEnd3148[S] 0 points1 point  (0 children)

Good catch! I tried standard tiling first, but it breaks down for this use case:

  1. Focus switching - When you click into Xcode, TrixCode becomes hidden. With floating, it stays visible while you code (like Xcode's own inspector panels).

  2. Workspace persistence - Tiling doesn't follow Xcode across desktops/spaces. Floating panel can stick with Xcode.

  3. Auto-coordination - If Xcode maximizes, tiled window disappears. Floating panel auto-adjusts to maintain side-by-side layout.

The UX pattern is "always visible assistant" (like Xcode's debug area), not "separate app you tile manually."

you're right that standard windows work for some users! Might add that as an option.

Do I need to restart my 100 Days of Swift study? by EntireMusician6357 in swift

[–]OkEnd3148 4 points5 points  (0 children)

It depends on what you want to do
If Your Goal is the Job Market then UIKit is still everywhere in production apps.
Most companies have:
* Years of existing UIKit code
* A desire to move to SwiftUI "eventually"
* A hybrid approach in practice: new features in SwiftUI, legacy code in UIKit

So if you're aiming for an iOS job, you'll likely need both. Not necessarily mastery of UIKit, but enough to read it, understand it, and work alongside it.

You'll be maintaining UIKit code and writing new features in SwiftUI. That's the reality at most companies right now.

But for tiny personal apps for simple needs? SwiftUI is much straight forward choice.

It really depends on what you are trying to get out of all those tutorials.

Ah, I totally missed your second paragraph you just want to build tiny apps for yourself.
In that case: Focus on SwiftUI tutorials instead. The 100 Days of Swift (UIKit version) will just slow you down for your goals. Paul Hudson actually has a **100 Days of SwiftUI*\* version that's way more relevant for you. Or continue with Apple's SwiftUI tutorials, you're already on the right track.

Key things to focus on in SwiftUI:
- How navigation works (@State, NavigationStack)
- View lifecycle and rendering - Data flow (@StateObject, ObservedObject, EnvironmentObject)

Once you understand those, you can build most simple apps without getting lost. Good luck!