About Droidcon #
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.
Selection Process #
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.
Offline support for business apps - WHY & HOW
Offline support for a mobile app nowadays has become an implicit expectaion. With lot of apps allowing users to do things, without thinking whether they are connected to the network, have intermittent or no network connection. This happens to most of us while traveling or in some areas which have sparse connectivity. Users would still expect the app to not throw them out completely, instead allow them to do things normally and let the app intelligently handle network related stuff when they are back online.
The talk will be focusing more on architecture of a system which can adapt to offline or online and talks about key components which you should think of when designing an app which doesnt die with no network.
There are couple of things which come to our mind, when we start thinking about making an app work in offline mode.
How do we keep the data consistent
How do we handle stale data
What is the frequency when we should sync the data.
What type of data and how much of data do we cache
Is there a threshold on how long can he be offline ( for critical transactional application)
How do we handle conflicts for multi edits on the same entity – Conflict resolution
How do we keep track of audit trails for business applications
We will be sharing our learnings and the key components and workflows to keep in mind to enable an app to work offline.
Speaker bio #
Working in Intuit as a Mobile developer developing Android apps.