WWDC 26 Conference Trip

Fly into SJC (San Jose) — closer to Apple Park than SFO. Book early, flights fill up fast around WWDC week.

Transfer to hotel in Cupertino or San Jose. Stay as close to Apple Park as possible — you will be making this trip every morning.

Check in. Confirm your Apple Park entry details and download the Apple Developer app if you have not already.

Prep: finalize your WWDC session wishlist, set up your schedule in the Apple Developer app, and book any lab appointments that open today.

Sunday pre-WWDC community dinner. Unofficial developer dinners and parties happen around Cupertino and San Jose on Sunday night. Research and book in advance — these are some of the best networking opportunities of the week.

Early breakfast. Doors open early and lines form fast. Do not underestimate the crowd size.

Travel to Apple Park. Allow significantly more time than Maps suggests — thousands of attendees arrive simultaneously. Factor in parking or shuttle queues.

WWDC Keynote at Apple Park Amphitheater. Arrive at your seat early. Take notes on anything directly relevant to your app stack.

Lunch. Good time to process the keynote announcements and compare notes with other developers.

Platforms State of the Union. More technical than the keynote and more relevant for developers. Do not skip this — it covers the APIs and frameworks in depth.

Post-keynote notes: capture your immediate reactions and what the announcements mean for your app specifically. New SwiftUI APIs, framework changes, deprecations. Do this while it is fresh.

Keynote night community dinner. One of the best nights of the week for developer networking. Many informal gatherings happen around San Jose and Cupertino — look for announcements on social media and the developer community channels.

Breakfast.

Travel to Apple Park.

Morning sessions. Pre-select the ones most relevant to your stack from the Apple Developer app. Sessions are also recorded and available later — prioritize the ones where you have follow-up questions for labs.

Lunch.

Labs. Book appointments in advance through the Apple Developer app — these are 1:1 sessions with Apple engineers and are the most valuable part of WWDC for indie developers. Come prepared with specific questions and code samples.

End of day notes: consolidate session takeaways and any API changes or lab feedback relevant to your app. Do this before dinner while detail is fresh.

Community dinner. Sit with different people than last night.

Breakfast.

Travel to Apple Park.

Priority lab appointments. If there are SwiftUI, CloudKit, StoreKit, or any framework labs relevant to your app, book them here. These slots go fast — book as early as the system allows.

Sessions. Focus on deep-dive technical sessions that complement your lab appointments.

Lunch with other indie developers. WWDC is one of the best networking events of the year for iOS indie founders. Be intentional about who you sit with.

Experiment: start testing new APIs relevant to your app while sessions are still fresh and Apple engineers are on-site to answer follow-up questions. Bring your MacBook.

Community dinner.

Breakfast.

Travel to Apple Park.

Remaining sessions. Prioritize anything you missed earlier in the week. Remember sessions are recorded so you can revisit them after WWDC.

Final lab slots if available. Last chance for direct Apple engineer access until next year.

Wrap-up notes: what are the 3 things you are building or changing based on this week? Write them down before the week blurs. This becomes your post-WWDC action list.

Log all trip expenses before tomorrow. Photograph any remaining receipts.

Farewell dinner with contacts made during the week. Book somewhere good — this is the last night.

Pack and check out.

Transfer to SJC or SFO depending on your return flight.

Return flight home. Write your post-WWDC action list and any follow-up emails on the plane while the week is still fresh.