| Name | GitHub | Challenge Response |
|---|---|---|
| Cue | @yuseongchae | Create a Swift Concurrency console log experiment that demonstrates how async/await handles Task execution through suspension and resumption, documented in a repository. |
| Juni | @dudwntjs | Design and implement an event-driven CoreBluetooth architecture using AsyncStream and a dedicated BLE Serial Queue.By doing so, analyze how the original Delegate-based architecture works and establish a baseline for improving its overall structure. |
| Sammy |
Anyone who is interested in exploring ideas through concurrency code - including Swift Concurrency - is welcome to apply, regardless of experience level.
To apply for the Concurrency Lab, select the application link in the internal announcement. and submit your response after writing your Challenge Statement, based on the provided Research Idea (Big Idea).
Using your Challenge Statement as a starting point, you’ll work with Jaesung to shape your Investigate direction and define your Challenge Response.
You’ll create a final outcome that can be shared on this repository, and spend the lab period carrying out your Act phase based on your Challenge Response.
| Phase | Duration |
|---|---|
| 📚 Investigate | 2 days |
| 🔬 Act | 10+ days (weekdays only) |
| 🎓 Epilogue | 1 day |
| Guiding Activities | Guiding Question |
|---|---|
| Get started with WWDC sessions | How can I find the appropriate Apple's development/design sessions for my Challenge? |
| Explore existing discussions in the open source community | What existing discussions or approaches are related to my challenge? Where are these discussions taking place? What gaps or opportunities have been discovered from the existing discussions or approaches? |
| Design code with diagrams | How can I define the structure of my code? How can I map out every branch, condition, and edge case in my logic before it becomes code? How can I trace method calls and data flow between objects at runtime? |
| Prepare to open great Pull Request | How can I help reviewers understand and review my Pull Requests effectively? |
| Looks Good to Me - Explore how to communicate for better code | How can I provide good reviews for Pull Requests? |