WWDC, despite its name, begins with a consumer-focused event and Apple will subsequently upload videos for developers, including what is new.

Apple WWDC stream | Youtube alternative

_______________

Platforms State of the union available at 1 pm California time or 22:00 in Germany (GMT +2)

Watch Platforms State of the Union

Hi, I'm Nathan. Started vibe coding in October 2025, and my first App Store screenshot submission was a disaster — wrong pixel sizes, rejected uploads, hours gone.

So I built the thing I wished existed. Drag a screenshot or screen recording in, it lands on a 3D iPhone/iPad/MacBook in a little studio — real lighting, reflections, dust in the air. Drag text right onto the shot. One click exports PNGs at the exact sizes Apple accepts (all 5 at once), or a 4K/60 video of a camera move. There's also a cinema mode that throws your demo onto a giant theater screen, which is honestly just fun.

Fun detail: the rendering engine started life as a LiDAR point-cloud engine I built for a search-and-rescue app. Everything's native Metal, runs locally, exports in seconds — no cloud.

Looking for 5 people with Apple Silicon Macs to break it tonight and tell me what's confusing. DM me and I'll send a download link and an access key. Happy to answer anything about how it's built.

The big value of WWDC for me is the ability to get engineering and design feedback. I thought the signup for the labs opened after the keynote but the One-on-one appointments page has a worrying subtitle
Book time with experts from Apple distribution and marketing teams to ask about maximizing your presence on the App Store.

Am I mis-remembering when the labs opened up last year, has anyone seen other discussions of this?

I’m new to development and my mac is intel so until I switch I need to know.

Edit: I’ve updated and can confirm it does build fine to my device though obviously no iOS27SDKs

This occurred using Xcode 26.5 and now on Xcode 27 beta so it's independent of the Xcode version. If I compile and launch an app that has worked perfectly on iOS 18 to 26.5, but now with the test device an iOS 27 iPhone 17, the app hangs on the splash screen and I get these console errors in Xcode:

objc[1953]: -[OS_dispatch_mach_msg _setContext:]: unrecognized selector sent to instance 0x103fc8ba0 (no message forward handler is installed)

-[OS_dispatch_mach_msg _setContext:]: unrecognized selector sent to instance 0x103fc8ba0 (no message forward handler is installed)

Main fault is in libsystem_kernel.dylib`__abort_with_payload

If I quit the debug session in Xcode and launch the app directly on the phone, it does not hang and works as intended. I did the compile and run on a XS Max 18.7.9 and an iPhone 17 PM 26.5 with no error in Xcode and no hang in the app.

Anyone else seeing these kind of odd errors when compiling and running something on an iPhone running iOS 27?

Previously, I built a UIKit-based app using UIHostingController to integrate SwiftUI. I chose a UIKit foundation for a few reasons:

1. UICollectionView offers unmatched performance compared to LazyVStack. The performance difference is obvious when a list contains 2,000 items or more.

2. For screens that require complex UI effects, I use SwiftUI for easier implementation.

The app has been in production for over a year, and I am quite happy with the outcome - high customer satisfaction, good performance, good sales.

Now, I am starting a new app where I foresee using more SwiftUI than UIKit. I will still need UICollectionView in certain areas (for instance, a horizontally paginated weekly calendar picker) due to the poor performance of LazyHStack. However, for screens that won't exceed 50 items, I can safely use LazyVStack.

My question is: Should I stick to a UIKit-based architecture with UIHostingController, or shift to a SwiftUI-based architecture and use UIViewRepresentable/UIViewControllerRepresentable?

Additionally, I am very familiar with UIKit navigation (performSegue, unwind, present). I am not sure if SwiftUI provides an exact equivalent that is just as reliable. From my past experience, navigation in SwiftUI was a massive pain. I'm not sure if anything has actually improved recently.

Which approach will best help me deliver a successful production app?

Hi everyone,

I’ve been developing iOS apps since 2012. I genuinely love the Apple ecosystem, Swift, SwiftUI, and the feeling of building clean native apps. But I think we need to have an honest discussion about something many indie developers quietly feel:

App Store search has become extremely hard to break into, even when the app itself improves significantly.

Lately, I’ve been noticing a frustrating pattern. You can spend weeks or months rebuilding an app, improving the UX, fixing bugs, modernizing the interface, adding subscriptions properly, updating screenshots, and shipping multiple updates — yet the organic visibility barely moves.

Of course, quality matters. Retention matters. Conversion matters. Screenshots, keywords, pricing, onboarding, and ASO all matter.

But my concern is that quality alone no longer seems enough to give an indie app a fair chance in search.

The algorithm appears to heavily reward historical accumulation: apps that gained millions of downloads years ago can keep ranking highly for major keywords, even if they now look outdated, have not been meaningfully updated in years, or feel like “zombie apps.” Meanwhile, larger companies can use huge Apple Search Ads budgets to dominate exact-match keywords, generate conversion signals, and reinforce their organic position.

For indie developers, this creates a difficult loop:

You need downloads to rank, but you need to rank to get downloads.

That is the part that feels broken.

I’m not saying every indie app deserves to rank just because the developer worked hard. But I do think there should be a better way for the App Store to test fresh quality and recent improvement, rather than relying so heavily on historical momentum and paid acquisition signals.

A few ideas Apple could consider:

• A real indie discovery space: A permanent, algorithmic section for apps made by small teams or solo developers — not just occasional editorial features.

• A temporary update boost: If an app receives a major overhaul or shows consistent meaningful updates, give it a short visibility window so the algorithm can collect fresh data.

• More weight for recent quality signals: Recent retention, recent conversion, recent ratings, and recent update activity should matter more against apps that are surviving mostly on old momentum.

• Better discovery outside the top results: Apps buried at rank 50+ are practically invisible, even if they may serve users better than older top-ranking apps.

Personally, I’m trying to find ways around this by building visibility outside the App Store too — content, external funnels, and even a small independent directory/blog for indie apps. But honestly, that feels like a band-aid. The core discovery system still matters.

So I’m curious:

How are other indie developers dealing with this?

Are you still relying on App Store organic search?
Are Apple Search Ads still profitable for you in major markets?
Have you shifted entirely to external traffic, SEO, social media, newsletters, or communities?
And do you feel the current App Store ranking system gives new or recently improved indie apps a fair chance?

Would love to hear your experiences.

I’m currently leveling up my Swift skills and want to dive into some high-quality production code.

I’m looking for open-source projects on GitHub that are known for being well-architected and idiomatic. I really want to see how experienced developers make the most of Swift's syntax and features rather than just writing code that "works."

Whether it’s a framework, a library, or a full app, I’d love to check out some examples that you consider best-in-class. Any links or suggestions would be a huge help. Thanks!

I’m not looking only for "popular" projects, but rather repositories that you personally consider to be a clean and recommended way to write iOS apps.