( MAKE YOUR SUBMISSION COUNT )
Call for Papers Submission Guidelines and Tips
Welcome! We’re excited to invite you to submit your session(s) for droidCon 2026, the premier conference series for Android devs around the world.
Before you click through to the submission form, please read these guidelines as they will help you focus your proposal and increase your chances of acceptance.
( THINGS TO CONSIDER )
Audience & Talk Level
The community has changed over the years and our audience has too. With fewer junior developers being onboarded, most attendees at droidCon have 5-10+ years of experience. We’re primarily seeking intermediate to advanced sessions, with a heavy emphasis on advanced talks. If your talk is introductory or covers topics that do not go beyond regurgitating existing documentation, it may not be a good fit for our events.
The audience is looking for compelling case studies, unique experiences, solutions that have been deployed at scale and actionable intellligence they can take back to their teams and implement.
( MAKE IT COUNT )
What we look for
-
Structure: Clear problem statement + solution + outcome achieved
-
Strong narrative: Real-world examples, what worked? / what didn't work?
-
Relevance to audience: Goes beyond the documentation
-
Key takeaways: Code examples, metrics, lessons learned - Focus on outcomes!
-
Inspiring: Provides a roadmap to become a better dev
( COMMON MISTAKES )
Why talks get rejected
Common Issue | Why It's a Problem | How to Fix It |
|---|---|---|
Abstract was written by AI | Abstracts written by AI cause reviewers to doubt your ability to deliver | Take time to think about the problem you faced → your approach → the result → key takeaways. Write these in your own words. |
Unclear target audience | Hard to gauge fit | Be sure to choose the correct level for your talk. If it is Advanced, please explain why |
Overloaded Abstract | Reviewers consider if your session fits the length of the talk format | Plan the session abstract and detail level to fit the duration of your talk. See if your content fits the permitted time of Keynote, Lightning Talk, Session, or workshop. |
Too basic / introductory | Reviewers expect introductory talks to share useful insights | Focus on why it's hot, what problems it could potentially solve (at scale) , or lesson learned so far |
No clear takeaways | Reviewers want learning outcomes | Include 2–3 bullet points: “After this talk, you’ll learn…” |
Low-effort / Minimal abstract | Suggests low speaker engagement | Write your abstract with detail and adhere to the suggested guidelines |
Old / recycled content | The committee is looking for fresh and unique material | If you have given the talk before, please indicate significant changes or upgrades that have been made. |
Too theoretical / not enough real-world context | Developers want practical value | Include lessons learned, metrics, or implementation examples |
Vague or buzzword-heavy title | Reviewers can’t tell what you’ll cover | Use clear, concrete titles |
Product pitch / marketing | Conference talks should educate, not sell | Avoid brand promotion; focus on technology or experience |
( MAKE IT GREAT )
What makes a great talk?
Clear Learning Outcomes
Your audience expects actionable information they can use. Be sure to include ample code samples, resources or guidelines in your talk.
Material Should Reflect Difficulty Level
Align your presentation content with the selected difficulty level (Introductory, Intermediate, Advanced). This is the most common form of negative feedback regarding talks. If the difficulty level is not consistent with the rating, it results in disappointment.
Provide Perspective / Context
Explain the problem you're solving, how your solution helps, and its real-world impact. This context will help your audience understand and apply your material.
Practice Makes Perfect
Find friends, colleagues or local meetup and present your talk. Gather feedback on your slides from a trusted mentor. Make sure to prepare your slides well in advance.
