Everything you need to know about submitting a talk proposal for try! Swift Tokyo.
A comprehensive session covering a topic in depth. Include time for context, examples, and key takeaways. Live coding and demos are welcome!
A focused, fast-paced presentation covering a single concept, tool, or tip. Perfect for sharing quick wins or introducing new ideas.
A hands-on or lecture-style workshop in a morning (10:00–12:30) or afternoon (14:00–16:30) JST slot. Format and capacity will be arranged for each workshop.
A clear, descriptive title that accurately represents your talk content. English or Japanese is fine, or both (up to 100 characters in English, 60 in Japanese).
A summary that will be published on the website and in the app if your talk is accepted. This should explain what attendees will learn. English or Japanese is fine, or both (up to 500 characters in English, 300 in Japanese).
A detailed description of your talk for reviewers. Include your outline, key points, and any demos you plan to show. This helps us understand your vision. English or Japanese is fine, or both (up to 3000 characters in English, 2000 in Japanese).
Tell us about yourself! Your background, experience, and what makes you excited about this topic. It is shown on the website. English or Japanese is fine, or both (up to 500 characters in English, 300 in Japanese).
Share a link to a video of a talk you have given. It doesn't have to be a conference talk: a local meetup recording made with the organizer's permission, or a recording you made yourself on your Mac, works too.
URLs of your X, LinkedIn, Bluesky, Mastodon, or personal website (starting with https://).
Any additional information for organizers, such as accessibility needs, scheduling constraints, or whether you've given this talk before.
When choosing Workshop, include learning outcomes, an agenda, participant prerequisites and requirements, required software and hardware, materials, facilities, preferred capacity, and co-instructors.
Our review committee evaluates proposals based on:
