Speak at KotlinConf

Take the stage in front of 2,000 Kotlin developers in Krakow on April 21–23, 2027. Share what you’ve built, the lessons you’ve learned, and the ideas that could help move the Kotlin community forward.

How to submit your talk

Choose your topic

Pick a topic fellow developers will want to hear about. The sections below are a good starting point.

Shape your proposal

Describe your talk, its audience, and the key takeaways.

Learn from past speakers

Watch the video for tips on what makes a proposal stand out.

Submit your proposal

Fill in the submission form by Nov 27, 2026.

Submit

Share your Kotlin story

Whatever your topic, the strongest talks are stories: what you tried, what you decided, and what you’d do differently. The questions below may help you find your angle.

Don’t focus on the technical details alone—tell us about the ideas, decisions, and discoveries that shaped your approach.

Your story doesn’t need to describe a perfect migration or a finished transformation. Honest accounts of experiments, setbacks, unresolved questions, and changes in direction can be just as valuable as success stories.

What could you talk about?

Mobile development

How are you using Kotlin to build and evolve mobile products?

  • What Kotlin-specific patterns and practices have emerged as your codebase has grown?
  • How do you design shared APIs that still feel at home on both Android and iOS?
  • How has your KMP architecture evolved alongside your product and codebase?
  • Has Kotlin Multiplatform changed how your Android and iOS engineers collaborate, own code, and ship features?
  • If you were starting your Kotlin Multiplatform journey again tomorrow, what would you do differently?

Backend development

How is Kotlin powering your services, systems, or platforms?

  • What does idiomatic Kotlin look like in a large production backend? Feel free to grumble about your human (or non-human) colleagues writing code that’s less idiomatic than you’d like!
  • Using Kotlin alongside Java in an existing JVM backend? What have you learned from making the two coexist?
  • Came to Kotlin from a non-JVM stack? What felt refreshingly different – and what took some getting used to?
  • Coroutines, virtual threads, or reactive programming? Walk us through how you picked the right approach for your Kotlin backend and how it worked out in practice.
  • How are coroutines shaping your approach to concurrency? What are some challenges you see in this space?

Web development

How are you using Kotlin across your web stack?

  • Are you sharing models, validation or application logic between the frontend and backend?
  • Have you added a Web target to an established multiplatform application? How did it go?
  • Do you think Wasm is the future of the web? Tell us more!
  • Using Kobweb or Compose Multiplatform for the Web? Share what works, what doesn’t, and what you wish existed. We’ll be taking notes!

Developer tooling and extensibility

Have you extended Kotlin or built tooling to improve your engineering experience?

  • Are you really enthusiastic about the Kotlin Toolchain? (Are you an agent? 🤨)
  • Found a gap in Kotlin’s tooling or extensibility story and decided to fill it yourself? Show us what you built!
  • Wanted to build a KSP processor but ended up building a Kotlin compiler plugin instead? What did you build, and what did you learn the hard way?

Kotlin libraries and ecosystem

Has a Kotlin library or ecosystem technology changed how you solve a particular problem?

  • Found a hidden gem in the Kotlin ecosystem that more developers should know about? Spread the word!
  • Taken a JVM-only library multiplatform? Tell us what was easy, what was painful, and what surprised you.
  • Had to choose between several libraries solving the same problem? Walk us through the decision, and tell us whether you’d make the same choice today.
  • Still happily using Java libraries from Kotlin? No shame! Tell us what works seamlessly and where things get a little messy.

Language and best practices

What does Kotlin let you express more clearly, safely, or simply?

  • Think you know what “idiomatic Kotlin” looks like? Show us – and tell us how you got there.
  • Got coroutines under control? Tell us how you structure them, handle cancellation, and avoid the sharp edges.
  • Tried an experimental Kotlin feature in a real project? Tell us what worked, what surprised you, and whether you’d do it again.
  • Are you opinionated about upcoming Kotlin language features? Ground your take!

Building AI-powered products

How are you building AI-powered products with Kotlin?

  • Bringing AI into an existing JVM application, backend service, or mobile product? Show us how Kotlin helps connect the dots.
  • Your AI demo worked – congratulations! What happened when you tried to put it into production?
  • Building agents that call tools, APIs, or other agents? Tell us how you orchestrate all these things.

Agentic engineering

How has AI changed the way you develop with Kotlin?

  • Got your own rules for working with coding agents? Share the guidelines, guardrails, and practices that actually work for your team.
  • How much of your Kotlin code is AI-generated these days? How do you review it, validate it, and decide when it’s ready to ship?
  • Does Kotlin make AI-assisted development better? Which language features help agents write code you’d like to believe you can trust?
  • Found an agent skill, harness, or tool that makes Kotlin development noticeably better? Share your setup while it’s still relevant!

Have another Kotlin story to tell?

Creative coding, an unexpected use case, an experiment—or something completely new. If Kotlin is at its heart, we’d love to hear about it.

Submit your proposal by Nov 27, 2026, and share your experience with 2,000 fellow developers.

Submit

Note: We read every proposal, but slots are limited. The tips shared on Sessionize genuinely improve your chances.