droidconIN 2016

The sixth edition of droidconIN

Sixth edition of droidconIN.

droidconIN is part of the world wide series of conferences that happens in London, Paris, Berlin, Netherlands, Tunis, Ankara and Brussels. The first edition of droidconIN was at Bangalore in Nov 2011. The second edition in Nov 2012 was featuring General & Specialized Topics, Native + HTML5 and App Demos. The 2013 edition was about Systems, UX, Gaming, Business and App Demos. The 2014 edition featured dedicated tracks for deep dives into UI/UX, Data sync & versioning, App Demos and hardware. The 2015 edition had advanced technical talks with an emphasis on developing for resource contraint regions like India.


This edition spans two days of talks. We are inviting talk proposals for:

  • Full-length 40 minute talks.
  • Crisp 15 minute talks.
  • Sponsored sessions, 40 minute and 15 minute durations (limited slots available; subject to editorial scrutiny and approval).
  • Hands-on Workshop sessions, 3 and 6 hour duration.

Selection process

Proposals will be filtered and shortlisted by an editorial panel. We urge you to add links to videos / slide decks when submitting proposals. This will help us understand your past speaking experience. Blurbs or blog posts covering the relevance of a particular problem statement and how it is tackled will help the editorial panel better judge your proposals.

Selection process is stringent and we follow the procedure outlined in this flowchart:
Selection Process Flowchart

A talk is NOT confirmed till speakers recieve explicit communication from us saying that it is.

A talk can be rejected at any stage by us if we feel the speaker will not fit in the conference for the year. A talk can be canceled by the speaker at any time for any reason. (We would appreciate it, of course, if it isn’t at the last moment.) Please note that selected speakers must mandatorily participate in two rounds of rehearsals before the conference. This not only helps us adhere to the HasGeek format and quality, but also helps speakers prepare better for the intended audience.

There is only one speaker per session. Entry is free for those who are selected. Due to budgetary constraints, we prefer speakers closer to home. But if we think you stand out, we’ll provide a grant to cover part of your travel and accommodation to Bangalore. Grants are limited and are made available to speakers delivering full sessions (40 minutes or longer) only.


Updated (6th September, 2016): We are currently looking for talks in the following topics:

  • Toolchains - What’s the latest in developer toolkits to help with build systems (Gradle, Buck, etc), speeding up the dev feedback loop, etc.
  • Kotlin - An experienced speaker to help breakdown what Kotlin is, why and who should use it.
  • Firebase - A case study of Firebase in an medium/large app, with insights on it’s benefits, drawbacks, and when/where it makes sense.
  • Everything else - Anything else of relevance to an Android developer that we might have missed out.

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 for it to be available under a permissive open source licence. If your software is commercially licensed or available under a combination of commercial and restrictive open source licences (such as the various forms of the GPL), please consider picking up a sponsorship. We recognise 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.

For more information about speaking proposals, tickets, and sponsorships, contact info@hasgeek.com or call +91-7676332020.

##Important dates
Deadline for submitting proposals:

  • Proposal submission deadline(updated): 19 September 2016
  • Schedule announcement: 10 October 2016
  • Conference dates: 10 and 11 November 2016

We expect you to submit an outline of your proposed talk – either in the form of a mind map, a text document or draft slides along with your submission. You can edit your submission at any time.

##Proposal submissions are now closed.

Hosted by

droidconIN is an annual conference on Android, part of the worldwide series of events. more

Hardik Trivedi


Messaging Queue in IoT

Submitted Sep 18, 2016

In the growing world of IoT we need assured connection between to devices to communicate over the internet, where two devices push the messages to each other. To solve this problem Web Sockets, different push message mechanism like GCM/FCM and APNS are not always best. We need MQTT(Message Queuing Telemetry Transport) which is specially designed to consume low power and guaranteed delivery of messages. And to complete the push messaging infrastructure we need message broker, RabbitMq is the one.


Talk will be based on how to solve key problem which is communication connection protocol between two machines. When it comes to device to device communication and special when devices are not that capable enough in terms of processing and power utilization. Mostly they remains sensors attached with processing boards like Raspberry pi and Arduino. So HTTP and Sockets are not good choice to work with such hardwares. Rather than we should use MQTT protocol to such machine to machine communication. Its publish and subscribe mechanism is just so perfect for sensor application. Expect and cater for Low Bandwidth, High Latency , High cost networks. Its expects that client applications may have very limited processing resources available and solves the problem in best way. Provides traditional messaging qualities of service where the environment allows.

• Some highlighted point of Protocol
• Low complexity and footprints
• Simple publish and subscribe messaging mechanism
• Asynchronous delivery of messages to application
• Simple verbs like connect, publish, unsubscribe and disconnect
• Plain yet array message payload
• No message headers
• Smallest possible packet size 2 bytes
• In built constructs to support loss of contact between client and server

Now MQTT simply solves our communication problem. What about a message broker which will act as a mediator between those two devices. Broker’s task is to keep track of registered devices and maintaining mapping between two devices. RabbitMQ is the message broker which will help us to control our own message queue, which is robust mechanism behind guaranteed delivery of messages.

Speaker bio

I am Hardik Trivedi, I am computer program writer mainly spent my time writing robust android applications. In spare time I prefer to teach college students and professionals. I have been associated with multiple online institutions who offers cources for online study. I have conducted a webinar you can find the link in the link’s section.

Glimpse of my work :
Github : https://github.com/hardik-trivedi
Blog : https://trivedihardik.wordpress.com/
Website : https://branded.me/hardiktrivedi


{{ gettext('Login to leave a comment') }}

{{ gettext('Post a comment…') }}
{{ gettext('New comment') }}
{{ formTitle }}

{{ errorMsg }}

{{ gettext('No comments posted yet') }}

Hosted by

droidconIN is an annual conference on Android, part of the worldwide series of events. more