Droidcon is India's largest Android developer conference, and is part of the world wide series of conferences that happens in London, Paris, Berlin, Netherlands, Tunis, Ankara and Brussels. If you are doing anything with Android, you'd want to be here in Bangalore on Nov 28-30th 2013.
A WIP schedule will be up on the Droidcon India website and will be updated periodically.
Voting is open to attendees who have purchased event tickets. If there is a proposal you find notable, please vote for it and leave a comment to initiate discussions. Your vote will be reflected immediately, but will be counted towards selections only if you hold a ticket. Proposals will also be evaluated by a program committee, consisting of:
- Aravind Krishnaswamy of Levitum is the Program Chair
- Amrit Sanjeev of Intuit and Blrdroid will run the App Demos track.
- Kumar Rangarajan of LittleEyeLabs will run the Systems track.
- Rahul Gonsalves of UnCommon will run the UX track.
- Aravind Krishnaswamy of Levitum will run the Business track.
- Ravi Korukonda of PurpleTalk will run the Gaming track.
- Soham Mondal of Triveous and Blrdroid will run the Workshops.
Proposers must submit presentation drafts as part of the selection process to ensure that the talk is in line with the original proposal, and to help the program committee build a strong line-up for the event.
Final date for submission of proposals Oct 18th, 2013.
First set of pre-confirmations Oct 18th, 2013.
Submission of slide drafts Oct 25th, 2013.
Second set of pre-confirmations Oct 26th, 2013.
Schedule draft posted on site Nov 4th, 2013
Final confirmations Nov 5th, 2013.
Final schedule Nov 8th, 2013
All speakers are requested to be available for officehours during the conference. This will be a scheduled 30 minute block of time during which attendees can meet you at a designated space for open Q&A offstage.
There is only one speaker per session. Attendance is free for selected speakers. HasGeek will cover your travel to and accommodation in Bangalore from anywhere in the world for speakers delivering full sessions (30 minutes or longer). As our budget is limited, we will prefer speakers from locations closer home, but will do our best to cover for anyone exceptional. If you are able to raise support for your trip, we will count that as speaker travel sponsorship.
Commitment to open source
HasGeek believes in open source as the binding force of our community. If you are describing a codebase for developers to work with, we'd like it to be available under a permissive open source license. If your software is commercially licensed or available under a combination of commercial and restrictive open source licenses (such as the various forms of the GPL), please consider picking up a sponsorship. We recognize that there are valid reasons for commercial licensing, but ask that you support us in return for giving you an audience. Your session will be marked on the schedule as a sponsored session.
Non Accepted Proposals
If your proposal is accepted for a session > 30 minutes long, we will cover your event ticket.
If your proposal is not accepted, you can buy a ticket at the same rate as was available on the day you proposed. We’ll send you a code.
Android Build Process Using Robolectic, Maven/Gradle And Travis CI
This session aims to give a complete in depth knowledge of the android build Process. Attendees will get to know about how they could unit test their android applications using Robolectric, how to write build scripts for automizing their build process using maven & gradle, how to setup Travis CI for the Android projects and and how to automatically deploy your application to amazon S3 buckets on succesful build. There will also be a live demo of the whole process starting from commiting our code, continuous integration with travis CI, building our appication using gradle, running unit tests using robolectric and finally deploying the apk to S3 bucket.
This talk will take you through the journey of setting up the Android Build Process. Build Process plays a critical part in deploying our application from one environment to another. An automated build process bridges the gap between various steps involved in software development. I will talk about our experience in automizing build process for our android application framework at Artoo. The session will be focussed on the solutions of the problems that we faced in setting up the build process using different tools like Robolectric, Maven, Gradle and Travis CI. I will go through the following steps involved in the Android Build Process telling about the specific challenges one face at each of these steps
- Automated Unit Testing Using Robolectric.
- Using different build tools like Maven and Gradle and integrating them with Eclipse and Android Studio.
- Continuous Integration using Travis CI.
We are using these tools for building and testing out our android framework at Artoo. I have spent some 2 months setting up these tools and figuring out what works best and how ! We faced a lot of problems integrating these tools with one another to have a seamless workflow. We travelled from using maven & eclipse to using gradle and android studio. Right now all we do is commit our code and travis automatically picks the latest commit, run the build , unit tests the code and finally deploy it to Amazon S3. So we don’t need to worry about breaking existing features anymore while trying to deploy new ones. We can just code and the build process takes care of everything else.
If the participants want to try out the build process along with the demo, they need to have their systems with them. I will be making a github project for the session that will have all the prerequisites and setup in detail.
I work as an Android developer at Artoo IT solutions Pvt. Ltd. I hold a BTech in Computer Science and Engineering from IIIT-Hyderabad. I have worked as a summer intern at the Institute for Development and Research in Banking Technology, Hyderabad. I have been associated with BlrDroid Teach for quite a few months as a volunteer for taking hands on sessions on Android.