“A Summary of the WWDC26 Group Lab”

You can get started with understanding Custom Product Pages with the resources below. These are great places to begin: Custom Product Pages Overview Tech Talk: Custom Product Pages There are also some exciting updates coming to the Product Page. Check out the WWDC26 session for a look at what's ahead: Enhance Your Presence on the App Store

Hello @KenZakreski, Is your question related to the LiveCommunicationKit and Push-To-Talk features announced at this WWDC26? For questions about other frameworks, you might want to make a dedicated post in that topic. For tips on creating a forum post see Tips on Creating a Forum Post! If we are mistaken, please rephrase your question. Thank you for your post!  Travis

try Core Data Lab https://betamagic.nl/products/coredatalab.html

In addition to the .photos.addAssetsToAlbum, you will need to adopt the .photos.createAssets schema. To support incoming content in your app, you can add the Transferable protocol to the entity representing the incoming content. Then, use importing on the transferRepresentation of that entity. See these sessions for more information on Transferable. WWDC26 session Build intelligent Siri experiences with App Schemas WWDC24 session What's new in App Intents

Enquired about this during a lab session at WWDC and you cannot get multiple camera streams.

This is the gap everyone building on PCC needs answered. Based on what was discussed at the WWDC26 ML labs, here's the practical reality: When you cross the free PCC threshold, Apple hasn't published a paid fallback program — which means you can't rely on PCC scaling automatically for a commercial app at volume. The safe architecture today is to build the fallback in before you ship, not after you hit the limit. The pattern that holds up: abstract your inference behind a protocol so the model tier is swappable. Route to on-device first where the task allows it (free, no threshold), use PCC for the cases that genuinely need it, and have a third-party provider (via the Language Model protocol) configured as the overflow path for when you exceed PCC eligibility. The new Language Model protocol makes this swap close to a one-line change. The architectural principle: don't let PCC be a single point of failure your business depends on with no defined cost ceiling. Treat it as one tier in a routing

I tried to get a WWDC lab about this issue but the request was rejected.

the same issue on home lab server through reverse proxy annoying