Droidcon is a two day international conference that's all about Android. It brings together luminaries from all aspects of the Android ecosystem - solo app developers, visual and interaction designers, software startups, enterprise software leaders, robotics and arduino wizards, kernel and ROM hackers, OEMs and platform providers, and technology enthusiasts.
Tickets are available from droidcon.doattend.com.
Proposal Selection Process
The proposal funnel below will enable you to submit a session and vote on proposed sessions. It is a good practice introduce yourself and share details about your work as well as the subject of your talk while proposing a session.
Each community member can vote for or against a talk. A vote from each member of the Program Committee is equivalent to two community votes. Both types of votes will be considered for final speaker selection.
It's useful to keep a few guidelines in mind while submitting proposals:
Describe how to use something that is available under a liberal open source license. Participants can use this without having to pay you anything.
Tell a story of how you did something. If it involves commercial tools, please explain why they made sense.
Buy a slot to pitch whatever commercial tool you are backing.
Making a funnel submission does not guarantee final selection. While selected speakers will get a free ticket to both days of the event, proposers whose talks are not on the final schedule will be able to purchase tickets at the Early Geek price of Rs. 1800.
Sessions at this year's Droidcon are 30 minutes each, including transition time. You have 20 minutes to present and 5 minutes for Q&A, with the remaining 5 minutes for the next presenter to begin setting up while you answer the last set of questions.
If you have material that will need more than 30 minutes, consider:
- Skipping the first part of your presentation and making it more advanced level, or
- Splitting it into two proposals. The Program Committee will work with you to schedule your (selected) sessions back-to-back for continuity.
The main overarching themes for this years Droidcon are grouped into five sections.
15 minute demo of app you've built (yourself or as part of a team)
30 minute deep dive into one specific unique problem you dealt with and how you solved it. Problem can be technical or UX.
15 minute Q&A
One spot will be reserved for a featured hacknight demo (or a short demo of all apps)
15 minutes of concepts via slides
30 minutes of show and tell
15 minutes of interactive guidance with audience
Topics should address specific areas - for instance a) Using Fragments, b) Building basic animations, c) Using WebView, d) Offline Storage & Cache.
Prior registration is required, all attendees must bring laptops with SDK & tools preinstalled.
Speakers must ensure sessions can be run without Wi-Fi access if needed.
NFC / Android Beam
DLNA & Media / Google TV
Enterprise App Development
UX Patterns & Challenges
Designing apps for the Indian market
Platforms, Tools & Libraries
Usage of open source platforms, tools & libraries like Eclipse, PhoneGap, Kirin, jQuery Mobile, etc. Proprietary tools need to be sponsored sessions.
Whats new in Jelly Bean
Designing for different form factors
Marketing & Monetizing Android Apps
The Program Committee may recommend that some proposals under General Topics be considered under the Workshops or Specialized Topics section depending on the nature of the content.
Writing Toolkits, Frameworks and Plugins. A Developer Masterclass in Writing Re-usable Code.
Software is eating other industries all over the world.
The strength of software, why it is so successful – its malleability, its lack of physicality, its repeatability – is also its Achilles Heal.
As developers of software, how do we respond to that? How do we turn those properties into our strengths?
This session is about the quest of elegance and writing as little code as possible. It aims to be a levelling up in their craft for intermediate and advanced developers looking to move from developer to senior to architect.
It will focus on writing toolkits and frameworks. You won’t need to be building them to appreciate these insights, but you may end up wanting to.
This is a tutorial session, which may require some amount of audience participation.
No suits allowed.
James is a successful and experienced software engineer. He has been writing software for 25 years, 4 of which on mobile, and has architected compilers, general purpose genetic algorithms, reasoning engines and latterly, Kirin.
He brings to this session opinions and a few facts. The opinions are bourne out of years of doing the failed experiments, over-engineering, making things you’re not going to need, and making mistakes so you don’t have to. The facts he looked up on Wikipedia.