 So, it's a tough act to follow, Kaushik, thank you Kaushik, there was, sorry, the center, okay, I'll pin it on there, there's a droid man there, tough act to follow but I'm gonna take a few minutes and I just wanted to get feedback from people really quickly as we start to plan DroidCon next year and we're trying to incorporate a lot of your feedback from last year into this year's DroidCon and wanted to get some feedback on just what you felt, we did well this year and potential area that you sort of think that you'd like to see us do a little more of, things that you'd like to see us do a little less of and any other sort of general items you have. So, I've got the sheet up here which hopefully you guys can all see, just sort of, you know, three four buckets. So, I'm the chair of the program committee working closely with you know, Amrit, Kingsley and Soham. So, I'm mostly looking for feedback with respect to content and but you know, I'm happy to capture feedback with respect to logistics and infrastructure which I can pass on to the Hasgeek team as well. Now, we did send out a feedback form so I know there's a lot of feedback we're kind of collecting anonymously but I also want to just open it out so in case there's sort of broad feedback that you've got, maybe not specific around you know like here's how Amrit session was or anything like that but just broad feedback about some things that we've done well that you'd like to see a little more of, something that you'd like to see a little less of since it'll help us to sort of plan out next year a little more. So, I think there's a couple of mics so one of the volunteers can just help just raise your hand if you'd like to chime in and you know, he'll help you out. So, anybody? I'd see a couple of hands up there, so where are you? Yeah, so I have, I noticed that we used those three Android for rating sessions in terms of beginner, intermediate and advanced. I think those were somewhere inappropriate because I attended and watched a lot of intermediate sessions that in my opinion should have been marked beginner and a lot of you know advanced session that should have been intermediate. So, I guess next year we, one of the things that we could do would be to ensure that a beginner session means somebody who's been probably say writing Android stuff for six months and an intermediate session means a significantly intermediate session. I mean, I don't want to, I personally would not want to see how to build layouts or you know things like that in an intermediate session because that is something that is, that would be more appropriate for somebody who's basic and advanced sessions would mean something that would specifically require me to rack my brains. Yeah. And you know, that's something that you rarely get to see. Yeah. That's something that I, that's good feedback. I think it's something to sort of struggle with, right? I mean, it's a, some speakers almost sort of prefer to put it down as being like a beginner session so they can reach a larger audience, even though some content's intermediate. And sort of speakers, self-assessment of whether the content is beginner, intermediate or advanced is sometimes off. And sometimes the thing is even though we review some of the slides with people, it's sometimes hard to sort of get to that level of detail from the committee standpoint to look into it. Completely agree. I think it's something where maybe, I don't know what you think, maybe we can put out some guidelines on what beginner, intermediate, advanced is. Would that be a good idea? Sure. Hi. I'm pretty much new to Android development. Only for the last two weeks I'm into Android development. Even I myself found the condense to be actually of too low in technical level. So it'd be better if you could add more in detail. In detail. That's good feedback. Let me welcome you next year to come forward and present. I'm sure you'd be a capable speaker by then as well. And also I felt that there were a lot of cross platform talks here. Maybe more Android related talks, more Android details than writing in cross-platform apps and deploying just to Android. I think we had out of a total of 38 sessions, we had four cross-platform talks. I agree it's 10% but cross-platform is important enough that there is a big team this year. But we had only about four or five. We had James, we had Gaurav and then we had two more. Some of the talks which really didn't talk about the cross-platform but sessions were more or less related to that. That's good feedback. But I guess I must state that this year one of the teams was cross-platform. Since increasingly that has been in demand from people because people are building apps across iOS and Android increasingly and looks like potentially Windows as well as maybe a team next year. But it's good feedback. What do you think that mix should be then? So if it's not, this year we had four out of 40. Got it. Fair enough. That makes sense. I suspect our team here will continue to be to have some mix of both because that is sort of interested population. What that mix is I'm sure we're open to feedback. But welcome good feedback there. So I think if nothing else, let's think about make your native. That's sort of what you're saying. Anything else? See a few hands. Could some mics go around, please. This is Raja. Very Raja. Pretty much overall, it's a good session. We are really happy more or less that Intel TI sessions. And of course, there are a lot of companies they have presented. It's pretty much it's very good. So what do you think we did well? Because I'd like to capture those two because we want to specifically tell you no problem. I don't want that into that. So but what I overall observed is mostly we have covered app side and that app side. Yeah. So it's what we thought over here is okay, maybe probably we will cover end to end of at least application processor point of view. Maybe we should cover a little bit of middleware side multimedia side. And even if somebody because all over came over here, it's mostly from the product OEM companies, right? So they can still some more point Linux kernel point of view on multimedia side, connectivity side, something what all the challenges they faced when they integrate all the connectivity, like Bluetooth, Wi-Fi, GPS, Agps, some one of the discussion they talked about GPS, but still a little more. Okay, because even that how the integration because app how integrated with the baseband processing, if somebody comes up that kind of things, it will give us okay, more challenges, what all the challenges, because Android is almost there in the industry more than four years now. On the app side, the basic and even today, the evening session, we talked about GCM, it's a new topic. So if you cover such a new ideas, new topic, which further down the two years down the line, this will pick up some more ideas rather than talking about till this Android app side, not much makes sense to just my feeling. Got it. Got it. So you feel that more systems oriented talks, which cover various systems areas would be benefit. So this year, we clearly had two themes, one around cross platform, one around app demos, show and tell, but these two didn't let us get into some areas of system related topics, which could have been of interest. That's good feedback. I think we'll. Yes, we had a lot more system talks last year. So the sort of a bit of a shift that way. And one thing I want to highlight too is some of this is driven by the funnel and the speakers who come forward to talk and the proposals that came out. We did sort of select the themes this year sort of saying, we're looking at app demos and cross platform. But we welcome topics in all sessions. But it's good feedback. I think we'll definitely keep it in mind too for next year. All the layers, so that actually who comes, if he's experienced or he has some ideas, he'll get more knowledge and who doesn't have, they'll get one exposure. Otherwise, we're actually staying at the layer where apps and somebody has already done it. So it's something like marketing. So we stop there. We need to actually go forward. And as Raja said that we need to think of two years down the line, what exactly, or even the latest vertical, the OS which has come up, how exactly how easy it is to implement or one session should be on workshop kind of thing that, okay, if you're interested in this topic, do on this. But there's a workshop working on so that you can go and try hands on getting a device and all that. Can I get both your names, please? Deepak and Raja, I need a favor. Can I request that both of you come forward with more systems related topics next year as the speakers? Yeah, done. Awesome. That'll be great. I think that's something we didn't get enough submissions this year. But those definitely have been in consideration if they had. And the other part of it too is the system related topics from the Shrikumar came forward with one. And I think it was one session with that. But there weren't enough upvotes in the other topics. So definitely your votes in the community matter. So definitely next year as a part of the cycle, please vote for talks that you're interested in. If you look at them, a lot of the app demos, they had like 30 plus votes in the funnel. And a lot of the other talks like four, five, six, seven. So unfortunately, we have to go by this since this is the guidance we go by, right? So please definitely look up for that. But good feedback. Hey. Yeah. Compared to last year, this year's website seems you know, more colorful or something. One of the things that I wanted to add, even though this was a product last year also, was that you don't get the slides. So currently you have a link, you have a nice layout showing all the topics. So in one page, even if last year's website now, I won't get the slides. So now I'm sitting here, I couldn't go to the ECM. Now I want to see what the final slides they've used. I know it is pointing to the funnel link, right? That has only the outline slide. So I guess it will be really good if you can in one page, I can go to any talk slide. If I can get a link to that, that will be awesome, I guess. Just turn this over to Kiran from Hasgeek. I think he can sort of talk through the site and the funnel and how to access that. So the funnel does have slides as one of the fields that we ask speakers to fill in. And after every event we ask speakers to go back and put the slides into the funnel. Most of them don't end up doing that and that's unfortunate, but that's beyond our control. It's up to speakers to do that. So speakers in the room, please do that. Please go back to funnel, edit your entry and add your slides over there. Even if you're using Impress.js, put it online and put a link over there. If it can be embedded, it will be embedded, otherwise just the link will be there. We do that every event. Yeah, in addition to doing that, quite honestly, we badger most of the speakers for the last couple of weeks before the conference saying, please send us your slides, please send us your slides. A couple of people here are probably begging for the last few weeks saying, hey look, let's look at your slides. We might have some feedback. So we definitely do that. I think we could probably do more of it. We could probably even sort of decline certain speakers who don't have the slides ready, but that's a little harsh. So it's a bit of the trade-off. So what eventually happens is you know some guys are good. They're probably busy, juggling a number of things. We want them to present. We kind of go a little easy on them. They don't have the slides uploaded in time. They pull it through in time for the conference and they make a great presentation here. So it's a bit of that trade-off. So a few of them don't make it in time on them, but we'll definitely send reminder notes out and hopefully they'll all put it out there. So those of you who are speakers here, here's a request from everyone here. They want to see your slides. Many of you have shared it on Twitter, but if you can upload it to the funnel with a link to your slides and slide share or wherever it is, I'm sure it will help everyone else later who would want to come back and check and see the slides that have access to the material. So basically, more than feedback, first of all, I want to tell that I'm not an Android developer. I haven't developed in quite a while, like in two, three years and I've never developed on an SDK, but I never felt out of place. So there has to be a huge round of applause for all the community members who have really worked hard. So it's not one of those geeky event where, you know, you start feeling out of place and I have landed up somewhere wrong or something of that sort. That's not there. One of the thing I wanted to extend app jam that we did, maybe. So what exactly can happen more than gratification is people want to make their idea live rather than getting gifted for that. So what you can do is like reduce the five minute into two and everybody should come up with a Twitter hashtag. So what happens is like, for example, I go to the stage and I deliver my idea. Some of the developers are interested to work with me, but it dies down. So basically I come up and I have a hashtag in mind. So whoever wants to contribute, just tweet to me and then, you know, we all can get together because there are lots of developers who can't develop everything alone. Development is not about you sit down and code everything yourself. It's about collaborative efforts. So Twitter is there and virtually everybody in this room I think is on Twitter or if you're not, I mean, you should. So but it's a very easy way to so basically instead of five, you go to two minutes, you go there, you present your idea, come down. If somebody wants to really like and work with you, they can tweet on that hashtag and maybe it's a good idea. I can have developers and it can really make it live. So more than any reward, the idea becoming live is much more rewarding. So I have a complaint regarding the mobile projectors. So it was not working as it required. So in an Android conference, you have to have a mobile projector which can project the mobile better so that people who want to give a live demo can do it in proper way. Yeah, my point, I just add that in logistics. Yeah, hi. I've been attending DroidCon over the past even the last year I attended and I should applaud you guys that the content in the sessions has grown so well over the last year that it was really nice attending it more than it was last time. So I think that's very nice. I want to applaud you guys on that. But I think one thing that needs to come in is this kind of more geek kind of sessions. I feel at least if you could have a stream of things that are going just into it. So the NDK and all that stuff, they announced one more something over the IO. I forgot the name of it. But I think we need to have more, probably not as mainstream sessions, but probably pods as such or something like that, wherein people can just go and get started or share their ideas with someone who's already in the pod or something like that, more on the collaborative with one another developer rather than just give sessions. No, completely agree. And so this is the sort of thing we really want to encourage. What we sort of struggle with, though, is some of these conversations need to happen. Now, and if you remember my first presentation, I sort of kicked off this year's DroidCon, I was really hoping people will attend lesser these sessions and find people with similar interests and collaborate on some of these things. So the hard part is, ultimately, when you go through the funnel, some of these topics are not going to get them any votes. There might be four people, five people. But it's this thing of when you're at this conference, can you find each other? And this is a huge, beautiful place, right? I mean, there's enough space around here, additional rooms, lounges and so on. But what can we do to help more of you sort of come together while you're here? There are people from all over the country who have come together from Delhi and so on to help UX guys come together. People who are systems come together to have some of the separate conversations. You can whiteboard separately in a room, you know, just do different things together. We'd love to do that. And it doesn't need to be a session necessarily, sort of what you're saying. Completely agree. We want some ideas for how we can do it. And of course, you have to figure out whether you can manage the logistics of it too and so on. But we definitely want some ideas there. Sounds like you've got an idea. Can just add. If I mean, just one minute, I just want to add. Actually, if we can get in touch with you regarding that, I think we would like to help because we had a couple of ideas this time. But then we kind of had, you know, who to talk to and stuff like that. Yeah, that was a little drug-contrelated absolutely to me. I mean, any of the ideas with respect to how it was organized, logistics too, we can capture it here and take it offline Kiran or me, either way. That would be cool. Thanks. Hi. Speaking of collaboration, I had a couple of ideas to share. You know, I found it extremely challenging to, you know, interact with people within the audience because I don't know who they are, what their background is, where they're from, what are they here for? Yeah. And the irony is, I'm not even an engineer, but everyone I spoke to. And I mean, 10 out of 10 people that I must have spoken out of this entire audience said their primary goal of attending this event other than getting domain knowledge, which people here seem to have already figured out most of the things, was to actually meet others. But there is no format available in which I'm literally, you know, it's like just approaching someone very randomly and striking up a conversation. It might not be suitable to everyone's personality or inclination. So a couple of suggestions I can make for that. In the past, I've attended similar such conferences here and in Silicon Valley in California. One was like literally a board here, like a startup hub. For example, I attended an event which had a board with post-it like stickies and startup hub which said looking for jobs, people, funding. Something as simple as that. And it kind of required anyone and everyone to just put a little note with their contact information at the event, stick it there. Got it. Everyone can go there, look it up and say, okay, you're looking for a job or a person or funding and whatever the topics might be. And you can reach out to them. That was something which I found extremely valuable because it was at the event. That means everyone who's posting is necessarily at the event. And the other suggestion I had was another event which I had attended. For all those attending, like folks like myself, when we register or sign up for the event and we get our confirmations, on the web, there was an option to actually share your own information and know who's attending, what they're all about, what's their purpose. So through the web itself, and this was overseas, so it kind of allowed people to schedule something that I'm going to be attending this event on this day in this city. This is who I am. I've seen your background. I would love to connect with you when you're there and we can maybe find a few minutes to chat in the corner. I thought that really elevated the entire experience of the event because not all topics are relevant to everyone. But what is definitely relevant to everyone is I need to know who's sitting next to me. And now I've lost out my time because people have either left or maybe the topics don't interest them and the event's over. I just had a point to make. Hi. Hi. Firstly, it was very good because my first time attending DroidCon and I'm not an Android developer, but I love things that I've been that people spoke about and how they joined different platforms. The only thing that was a little problem I think even for the speakers was the 30-minute time frame that you guys have for each session because most of them wanted to show pieces of code that are very important for people who would want to use if not the same thing, at least the way that they have done it. And they skipped over that and also the demos that they were supposed to give. And another situation was where there are two interesting topics that are on the same time. You will until and unless I attend a session or know the person I wouldn't know what to attend and what not to. It's a different thing to go back and have a look at the videos but it's a totally different experience to sit there and actually see someone present it. So my suggestion would be firstly, I think if people are really interested you can spread it over to three days and just not two so that we have time with speakers to actually ask them questions and they can present their ideas completely because I think they've taken a lot of time to put in the effort to the slides and the demos and the code that they have written probably just for this event so that they can share along with the other people. So I really think we need to respect them for what they are doing as well because today the events I attended most of them didn't have time just went through the whole thing. So I next draw it I would probably want to see that. Yeah. So sort of two points in the feedback the second one and let's sort of get in chime in a bit on. So the first one was sort of around the 30 minute thing. So this is a tough one. Right. We have had some speakers over the last two days who have actually finished in 10 minutes, 15 minutes even though they had 30 and initially they might have been allocated 45. So ultimately different speakers take different amounts of time and ultimately sort of the combination of the stage and everything else causes some people to talk a little faster. It's a little hard to gauge and the some speakers who until last night weren't even sure they needed the whole half hour. So it's a bit of a mix bad. It is hard. I'm sorry. I'll just quickly finish the screen. I'll let you just 15 minutes. Sorry. Several of the sessions were just 15 minutes. Absolutely. Several of the sessions were just 15 minutes. So we did have a few speakers who took the whole half hour. Completely agree. Now what we had sort of spoken to them about is that they had enough content for a full half hour to consider spreading it into two half hour sessions and take a full one hour. So we had four or five of those as well as you know we had James's session which is a full one hour and really engaging sort of philosophical talk about design and how to build components which hopefully was an inspiration for a lot of people here thinking of designing and building platforms and frameworks contributing to open source and so on. Soham did a workshop for about an hour. So we ensured those happened as well. We really believe that half an hour is the right spot. It sort of pushes people to try to just get the key concepts in and then open it up to questions, share insights because ultimately it's not a training session, right? 30 minutes. You can't go through a whole thing in code. You're trying to do a workshop that's a different thing and workshops can be one hour no problem. So I think I don't think that's going to change. I think we'll probably stick to a half hour. Our feeling and overall feedback is it actually worked well. So with respect to two days versus three days can only want to chime in. So the main thing that comes up with that is the cost. To give you a sense, what is your average monthly electricity bill? What's your monthly electricity bill on average? For some people it's 200. It goes all the way up to 1000 depending on the size of the house you live in. Now take a guess at what the electricity bill for this venue is for one day. I signed the bill yesterday so I know what it is. It's 24,000 rupees per day. That's how much electricity we're consuming on a per day basis. And you add one more day. That's that much more cost. Now that's actually the trivial part of the cost. The overall cost of the venue comes out to about 1.6 lakhs per day. Who's paying for it? You are. It's your ticket money that's paying for this venue. So basically to make it three days will just mean that your ticket gets a lot much more expensive which means fewer people are willing to pay that. And that is the trade off. You have to optimize for how much will someone be willing to pay versus at what level do you say that I'm sorry but you can't attend two parallel tracks or you can't attend three parallel tracks or can you make it four so that we don't have to take a venue for that many more days. And that optimization changes over time. If it turns out that the general attendee at an event is willing to pay a little more then you can say okay let's bump up the quality a little more. And that trade off is unfortunately not based on what any one of us as an individual is willing to spend on but rather about what the larger audience is willing to spend on and that's a very difficult guess to make because it's also a guess that I need to make one year in advance. So right now we're making the bet. The next year's doidkan is going to be three days. I may be wrong. It could be a four day event. I don't know but I'll only find out next year because I need to make that bet right now when I go book the venue. And that is an unfortunate problem. So it's not an easy problem to solve. Yeah and combined with that the thing of how do you align all these tracks together so it makes sense for people whose experiences and interests are so diverse right? You've got three tracks, couple of rooms to play with and people whose interests are beginner intermediate advanced across everything from UX to systems to apps doing specialized topics are doing no, there's a whole wide range. And you know, I've got my day job. I volunteer for the session when just this week there's two nights and I was up pretty much all night but trying to work the schedule or work through to confirm speakers, follow up with them. I think couple of days before I tried to drop the final schedule and I was up all night and it was a real struggle because we had to orient some tracks together and ultimately you have to balance some things. So couple of variables we try to balance right? One is we don't want people to keep hustling from one room to another. So we try to keep you in one room as much as possible. So that's why we sort of had the HTML5 cross-platform track and then we had some tracks around app demos and then we had some systems related talks that were in the other room there. So the smaller focus group could take those up. Now, when you mix those right? Among these, you've still got a few speakers who are very good, some who are a little newer. So then you sort of got to align and say, okay, what do we have two popular speakers out there at the same time? Then how do you kind of juggle those around? Once you've done that, you've got to figure out, okay, you've got a bunch of out-station speakers this year. This guy gets in at 11, but his flight comes in at nine. He might be a little late. I've got to move him to day two. So there's a whole bunch of those little moving pieces that add to it. And then people's plans change, as you know. So I'm just sort of saying, I'm not saying we can't improve there. I'm just saying it's just been a hard problem. We'll definitely hope to do better. Your feedback is valuable completely. I just wanted to share with you just some of the complexity behind it really. Who else? I think you've been raising your hand for a bit. Why don't I let you... Oh, right. Yes, please James. Hi, I've been privileged to speak to you guys in each of the rooms. And I've had a very long time to speak to you guys. So thank you very much for that. And also I've also been privileged to speak to people individually. So I don't know what the answer is to half an hour or an hour or whatever. Half an hour seems a bit short. An hour seems a bit long maybe. So maybe there's something in the middle to that. But really what I've grabbed the microphone for is to suggest a bar camp type idea. This would... People who are saying that we need better content or more good content. Bring it. Bring it yourself. I'd love to hear... I've had some great talks in the hallways. It would be good to bring that into rooms where we can have discussions or you present your stuff that you wanna talk about. And only just decide on the day or two days before that you actually wanna talk about rather than going through this curated and very sort of not quite stifling process of curation that you understandably have to go through. If you'd just give us a whiteboard or a projector and see what happens. Yeah, I'll let Kiran jump in on this. He's been a part of organising several of the bar camps in Bangalore. There's some things that I think work well with bar camp internationally. He's got some thoughts and maybe some things that don't necessarily always work at this scale. Kiran, maybe I'll let you chime in. So we have had bar camp Bangalore for many years now. It's... The 12th edition was a couple of months ago. And one of the things that's happened with bar camp itself now, given that this is the bar camp format that you come in and decide on who's going to speak where on the spot. There is no predefined agenda. And bar camp has gone through this process and come to the point where bar camp sessions are published online first. That even bar camp Bangalore says that we just can't handle the chaos of people coming in and saying that they'll speak on the spot. Please propose sessions online, work for them online. And your scheduling happens only when you turn up. But the fact that you have proposed a topic and you have got people interested is done before you come to the event. And that's unfortunately a function of the size of the event. That as anyone gets larger, it becomes really hard to do this kind of thing. And then again, there's also the problem with the venue. So this venue, for instance, has got this big hall here. Then there's one downstairs and there are two small halls in the back. So the fourth hall was going to be filled but it's been empty because we decided that we shouldn't have that many parallel tracks. And it's good. There was one hall left that you could say that this could be the open hall that anyone can go in and talk. We have tried this at other events in different venues where we had a little more space. And what we realized is that if it is not on the scheduled paper that you're holding in your hands, nobody goes to that room. So even when you've done event parties, if you do not put the party on the schedule, people don't turn up for it. So it's not about whether they're interested or not. It's about the fact that it is not legitimate until it's on the schedule. This is something that I've observed about audiences come to events in Bangalore. And that's an unfortunate thing. So the only way to do this is to say, let's see, find a mechanism by which you can push this onto the website or push this onto some kind of screen that people keep seeing updated content and say that that is a schedule as its current status is, as it's been updated. And that requires a bit more of technology to make that work. And that's work in progress. Yeah, I understand. The idea of how you manage the board, that's an implementation detail, really. It's the idea of having a smaller, lower bar at your entry. I mean, preparing slide decks is a lot of work. So if people come and have a round table discussion or much less in the eyes forward, but chairs in a circle type discussions, smaller rooms. And I understand that in this particular venue it's going to be difficult with a limited number of rooms that you have, but I think the meeting rooms downstairs would be quite interesting for that. So to sort of build on your idea, right? I mean, I think, so what Kiran's alluring to is, at this scale, ultimately some parts of it have to be organized up front. Or else people are going to come in and feel like, you know what, that's too chaotic, it wasn't organized, the speaker wasn't good, and so on. But maybe what we could potentially do is have one track bar camp style. Would that be something people are interested in? One track bar camp style. Like people understand what it means? Yep, it's quite a few people interested. So I think we can explore that. Maybe we can use the second room that's down there. Maybe consider it. Could be back. Thanks, James. Hi. I have another feedback with respect to people meeting up with each other. So we can have one hour on any one day, a fish bowl kind of a thing in the hall below. Like we had tables. So you assign three tracks. Maybe one track is whether cross-platform works or not. Or the other tracks has design principles or something. And people can actually come and discuss their issues and fight and debate. And I think that will really get their motors going. And just one session, maybe one hour session, on any one day, I think it will get people's motors going and you'll meet people who have similar interests to yours and similar experiences to yours and maybe share ideas, learn a little bit. So just one little thing on that in our room. You can say you go to each corner of the room. Acoustics becomes a problem. And this is one of the problems that's happened with BarCamp. That we have moved from venue to venue over time, learning that you just cannot have one big open hall with corner groups. You got to have some kind of physical separation to prevent sound from crossing over. Otherwise it just gets too noisy. So the hall downstairs fortunately is carpeted. So which means that it is not going to have an echo problem if everybody starts speaking up. And so that's something we could try. Although it's a bit of a risk. Until you try it, you don't know if it works or not because we've never had that many people try to talk in the room at once. Hey, I had some thoughts. So first, I think it's a good thing we've done more app demos this time. And I think it's a really good thing and we should continue to do more of that. More at once. Taking off from some of the suggestions and discussions about changing the format a little bit, the 30 minute versus one hour. I think 30 minutes is good. It allows people to introduce a topic. But it's very often, it's very difficult to get a technical topic and do a one hour presentation and convey a lot of information and that is just lost. A lot of information taken. And I think for those people who want deep dive in a particular area, right? Some of these ideas of doing a table discussion and things like that, a speaker can come up, introduce that topic, say it's a 30 minute topic and say, you know what? I'm sitting out here for an hour at a table designated downstairs. If people want to do a further deep dive, come and meet me. Or taking off from the idea of the design discussion, say Isaac had done a half an hour session on design principles. If he were to go downstairs and say, people want the app critiqued, why don't you come down? And I'll be sitting here and we can spend an hour or two hours, whatever, discussing and talking about this. So it's sort of a mixed format where speakers who want to volunteer their time in that way can. You can go in as a moderator, sit in and help with that discussion. Even if I'm not a speaker and I want to go help out, I might have some experience, I can go and do that. So it's sort of a discussion where there are a few people who are maybe semi-experts who can help with that discussion, there are beginners who are coming in. So it helps both in the collaboration, meeting new people, it also helps, you know, going deeper into a particular topic. Got it. And it doesn't have to be like set up a lot of tables in a room. A couple of tables, each is there for an hour or two designated to a particular speaker who has introduced this topic earlier and then he goes away to do a deep dive. Yeah. So I think a lot of this is sort of coming around to, sort of two pieces. James' feedback around how can we have less organization around some of the tracks and how can we have a little more organization around offline conversations. Yeah, sometimes, right? Sort of a combination of both, but it's good feedback. It's good. Yep. Who's got the mic? Hello. I attended Hack Night, I think last week. So it was part of that. All of you are welcome to Hack Night. It's awesome fun. Those who didn't make it this year, please make it make it. So it was really good. So I have one suggestion. What I found like in Hack Night to whoever came, most of the people were from Bangalore because it's difficult for the people come from outside. But in this event I found many people are from even Delhi, Hyderabad, Chennai, many places. So as we are a two day event, so will it be possible to have the Hack Night today? Because here it will solve the problem of workshop because here can people meet and solve the problem. Mentors will be here to resolve the issues next day. You see the point I hope I'm clear on that. So because we have the venue and we can crack the things because we learned, but we have not implemented. So it will be good if we try to do that in the night and if we get stuck and we get the help from the person who presented online. I don't know how feasible and how good the idea is. But that can be good for the people from outside also. They can enjoy what we enjoyed in the Hack Night. It's actually a great idea. I'm just gonna throw back one problem point at this. Should the Hack Night be on the first night or the second night? If it's on the first night, you're not gonna be awake the next day when there are talks going on. If it's on the second night, remember you're paying rent for the third day now. That means everybody's cost goes up. So that's the trade-off. The venue is actually pretty expensive. It's going to cost us about four lakhs for two days. Yeah, and somebody has to sleep at some point. Yeah, so. So simple guys, party at Kiran's place tonight. You guys are welcome, hack over, and I'm just kidding. So I don't know if you guys were up there, but a bunch of us were actually sitting and coding one night. Sorry, go ahead. No, a bunch of us were sitting and coding at night. Pratul and I were up till about two o'clock or so. I think Pratul was up much later. Dude, Pratul, how long were you up last night? What were you doing watching Cats in the auditorium last night? I was working on what was supposed to be the official DroidCon application. Which we'll see next year, so. Yeah, I'm sure. No, not next year. We'll see it in the next Hasgee event. So yeah, I mean, that was some of the points that people said that is what you're planning to solve with the application. And we hope. So that's what we were doing last night. We didn't announce this, but the venue was actually open all night. I think the sessions are really great. And I think everybody did a really great job at timekeeping, especially. I found that very useful. But one thing I just wanted to mention, so you guys are collecting feedback around the whole DroidCon thing. I'm pretty sure a lot of speakers will be interested in the feedback on the individual sessions as well. I don't know. Do you plan to share the feedback that you? That's a whole point of feedback. It goes to speakers. Will it go back to speakers? Yes, very much. All right. Yeah, I just wanted to make sure that there was a way that it would find it it's made back to speakers. So thank you. Absolutely. Oh, hi. I really love the event, first off. So you have these NFC cards, right? So I was at another event. They had like stickers, simple stickers. Like if you're interested, say AI or ML or you're just a beginner developer. NFC stickers? So yeah, just have the stickers. Not NFC stickers, not normal stickers, paper stickers. Just put them on your thing, just pick them up and put them on your thing. Oh, okay, well, if you see it, well, he's a red sticker guy. I can go talk to him, he's a VC, for example. And then the second thing is, if you want to have icebreakers and you could probably gamify it, many ideas here, gamification is possible. Like you already have NFC card and only a few companies are actually using the, give your contact information to them, right? So you could have something like the number of, the person who has the most contacts exchange just set up one NFC thing at one place and two people have to come there, hit their NFC card and their contacts will be exchanged. Later on it could be emailed, right? So that way, whoever wins could win something at the end. And trust me, a lot of people, the sales guys, will just make a lot of contact, would be nice. I'm gonna ask Sajat to answer that because he wrote the software. Thanks. I like the idea, it's actually quite cool. Just that we, the last moment, we also have a lot of firefighting with the NFC stuff because we're still figuring out a lot of issues with the design and architecture of the software that we wrote. One thing, the entire thing actually depends on the network at the venue and it always fails in the last moment. Well, you guys know that's how the conference Wi-Fi works, right? Thankfully we've figured out how to do it properly, at least like some, let's say we still, like 70, 80% properly in the last couple of events. So we're still sort of getting the NFC workflow properly and you know, so it would be great to talk to you about how you would be like thinking about, you know. Yeah, that's about it. So we actually built the contact exchange part of the software. It's a feature, it's just not out in public because we know it will fail randomly and we don't have enough data yet to make sure it works thoroughly because the network dependency is a serious problem right now. Yeah, so the other thing is we don't want to like promise features which won't work at the venue and you know, people start complaining. Yeah, and if you guys are doing work with NFC and Android, please come forward and talk about it last time. We were hoping for more speakers than NFC this time. I don't think we saw any proposals at all. So if you guys are doing NFC work, please come forward next time. So the other thing on the stickers, we actually had them at the hack night last week and we just forgot to print more. So they weren't enough to go around for everyone. That was the problem. Well, so just a suggestion, maybe you should consider freezing the talks a little while in advance before the conference. The reverse of last minute planning. Yeah, yeah, the rest I've given to them anyway. Absolutely. And it's, don't quite have an answer for that, man. It's, we announced the event a couple of months back and it's almost as, you know, as time tends to zero, the number of submissions sent to infinity. It's almost one of those equations. We just had a whole burst of submissions in the last two weeks. We sort of over straight off, should we say, note all those speakers, they've got good content, one of the tricky ones. What do you think? It should be more than an island one. So it's actually, I would say, I would take responsibility for the fact that it's been so last minute. And it's sort of an outcome of an experiment we've been running for the last few months, which is to see how much effort does it take to actually pull off an event at this scale? You know, a lot of event planning teams tend to do a whole year of planning and that's fairly inefficient. So part of what you've been trying to do is say, can we compress the planning cycle into a really short period and prove it to ourselves by actually running an event every week? And that's what we have been doing. Since September, every single weekend, since September, we have been doing a different event, different scales. Like JSP was two weeks ago, that again had about 320 people. And then there was Hack Night and then before that there was a JSP Hack Night and then before that there was an event where we went to UDP. There was one in Pune, there was one in Chennai, there was another one in Bangalore and so forth. And essentially the test for us was, can we just do one event every week and make it sustainable? And the outcome of the experiment? Yes, but then you have no weekends left. So that was one outcome. The second outcome is if you miss a deadline, you're screwed because this next event is a week away. And that's what happened with DroidCon. DroidCon missed two or three deadlines because it was the last event in the series. And usually what happens when it's the last event in the series is like, I'm worried about next week's event. I'm not worried about the next month's event. And thanks to that DroidCon ended up with a planning cycle that was actually only two weeks. So that's a learning. You know, it's possible to do events at short cycles and get your planning down to something that you can do effortlessly. But it is still not a good idea to do an event every week. But definitely agree that next year we should lock all this a lot earlier. And especially for those who are sort of traveling who have come in from remote places, it's not easy. You've had to plan, travel at the last minute. It's not easy. Definitely a room there for improvement. Yeah, what I can tell you is that next year's DroidCon is number 28, 29, and 30. Three days? Yeah. Okay. There you go. I actually have a question for Kiran, I think. Throughout the teaser website that was up before the actual website came up for DroidCon. So it was like pretty open-ended. Like had no information about the venue. Probably just wasn't finalized, but the tickets actually went for sale before the teaser, I mean the actual website came up. So for a lot of people who were like looking to buy the early birth tickets, so they had no idea about where the event is actually gonna happen. So if I'm buying a ticket, I need to do like, is it feasible for me to be there at that time and that date? And so, and there's no information or... That's a really valid point. That's what I meant by missed deadlines. The website was really missed. And then you can't do that website because it's another event that you need to pull the website out for. And that is the lesson that we learned. You know that don't try short planning cycles because these problems come up. That you have to also communicate with a lot of people who need time to make up their own minds about what they're doing at this time of the year, whether they're coming or not, or who else they're coming for and who else is going to convince them to come and so forth. And that requires so much more planning. And that's a bad lesson learned. That was a mistake. It was badly done. The communications didn't go out on time and I take responsibility for that. So I guess a small change that could be done for that is considering we already know the dates for DroidCon 2013. Put it on the website right now. Yeah, I guess you can put them on the website right now. Absolutely, it didn't go up today. People know, yeah. Are we through? Sure, please, yeah, go ahead. Need the mic or? I'd just like to end to say I think these guys did a wonderful job and I think we owe them a really big round of applause. Thanks guys. I think in just a few minutes we'll just run through to sort of really name all the people who have been a part of making this happen. I just had a few quick last things. I've made a note of all these. I want to validate just a few to ensure it's not just opinions of a few smaller groups of people. So the first is around more advanced sessions. So I think a couple of people here wanted that. So I just wanted to ask people how many of you think we need more beginner level sessions? Okay. How many of you think we need more advanced sessions? Got it, much more, much larger numbers. Now, how many of you think we need more of cross-platform, HTML5, mixed, native, related talks? Absolutely, okay. This feels like majority here. Small nickel there, but does that mean cross-platform as in integrating Android natively with say a JavaScript library and say Couch TV in the background? Or does that mean cross-platform as in Android, iOS and Windows 4? It could also be cross-platform but only in terms of strategy. And say how do you make parts of your code reusable, parts of your native, or how do you just screw it, I will just do phone gap or everything, or whatever else. Yeah, yes, cross-platform has the problem in itself. And say, what are the different ways in which you can tackle this problem? Absolutely. I mean, irrespective of whether you're a big company today or a small company today, right? One of the sort of challenges you face is time to market and getting either your startup app out there on all these platforms without one feature sort of lagging and feeling like it's a bastardized version. Or if you're a big company, right? Of really sort of ensuring that you have a good web experience and experiences across all those different platforms. So it's ultimately these pressures, right? Where we could live a year or two back in a world where we didn't need to worry about this a whole lot. Now ultimately, to really have native apps in each platform is a luxury that some large companies can have. But for a lot of medium-sized companies or companies that are smaller, they sort of treading this path of what can we do cross-platform? And it doesn't necessarily mean, you know, native shell with just HTML5. It could be a question of some choices, as I think the various speakers have taken us through. Maybe there's some postings with HTML5, some which are native. I don't think it's something we can escape as we go forward. And it's sort of one of the straight outs, what are the technology decisions we need to make? What should we really sort of equip ourselves with, right? We don't know what the future holds. Mark Zuckerberg made a very famous quote this year saying that, you know, betting on HTML5 is the biggest mistake that they made as a company, right? So who's gonna question him, right? But, you know, it's hard, right? We don't know what's coming up. Things shift fairly quickly in the space that we live in. So I think it's all of the platform to discuss it, see what's happening, and see how we can figure out what we can adapt to suit our needs. And whether it's across platforms, meaning iOS, Windows, Android, I think we've had requests for that too, to consider sort of a broader conference across these. Is that something potentially that interests some people? I don't know how many people here are both iOS and Android or other platform developers? Okay, that's like 40% I guess, roughly, so, sure. Okay, so I'm just gonna... Hey, just one question, Kiran, actually, this was a question for you. I don't know if it's feasible, but I think I speak for everyone when I say this, even though the event is basically now over, is there something that you could create on the Hasgeek side where people can come and just say, hey, I was there at DroidCon, and if people still wanna connect and know who they are, I think even though we're all on our way out, I'd still love to sort of have conversations with 80 or 90% of the people who have not yet met. Absolutely, so I've been trying to code this for a while, but with one event in a week, there's no time to do this. But now that this is the last event, I have three and a half months to the next event, that's the time to code and build these features. If I was a coder, I would have volunteered, but sorry. So, I mean, there's one thing we could do even now. So, people were asking me earlier today, why isn't DroidCon trending? So, the one way we could make it trending, all of us right now, if you just wanna say hi to people on Twitter, tell people what you do, if you wanna connect with other people and meet people offline in the hallway here. Hasgeek.com. Hasgeek.com, go for it. And say hi to folks now with the Hasgeek.com hashtag and tell them you're gonna meet them offline at 6.30 and in the hallway. Hi, before you move on, quick suggestion there. Lanyard might help there. Oh, hey there. There's a London based startup called Lanyard, which is really about conferences and it's Twitter backed. So, it's backed by Twitter data rather than money. So, you guys saying, let's all go to Lanyard and register there or register our details or whatever to say that we went to DroidCon India. Then I think that would be a useful stair to start with without touching any code. Yep, actually, Lanyard's a great resource. So, who's never heard of Lanyard.com? Okay, check it out, L-A-N, never heard of it. You have no idea what Lanyard.com is. Okay, so for you guys, go to Lanyard.com, L-A-N-Y-R-D.com, if you have internet, you can open that. Lanyard.com is an event planning wiki. It's where we list all our events. So, if you want to see the calendar of Haskeek events all the way through 2013, it's already on the website. Just go have a look and, well, yeah. See, this sort of thing happens all the time. You can go there and go to the DroidCon event page on Lanyard and say that you were there. And that's a clear way to find people because it uses your Twitter ID. So, your ID on Lanyard is your ID on Twitter. It's very easy to then go discover someone and go start a conversation with them on Twitter. So, that's a great site and people should use it. So, have you done this feedback? Anyone else got a point to make? That's a good question. So, how many of you here are actually programmers? Most of the audience. Not a programmer. Kiran Dries is here, notice. Sorry. I mean, I'm just leading by example. Just a few last things. This is one of the things that we sort of have some trade-offs of, which is getting big name speakers, versus trying to facilitate more interactions between all of you. Because to get big name speaker means sort of, bigger budgets, investing more money in it, planning a lot of their travel and things up front. What's your feel with sort of the mix, with sort of speakers we have, should we be reaching out to more big name speakers? People are sort of known more in the Android world. Is there something you'd like to see more of? Hi. Yeah, so about the speakers, I was just wondering, why don't you guys, like is there any reason you don't support like speaker prizes? Because that would attract a lot of people. What's the speaker prize? Like who, we can vote for the best speaker here. So, it's a great idea actually. Yeah, basically like a simple vote, even if it, not to like promote them, no prizes or anything, just like appreciation that you did a fabulous job. So, we actually tell the speaker that, because we look at the feedback and the best guy we make sure we inform them that they were really good. I mean, it would be nice if we knew it right in front of us, you know. It's paper feedback, man. Somebody has to do it right. That's what the man's been coding all night. It's not done, you know. Unfortunately, it takes a lot of time to build such features. We have in fact had two people, two different teams trying to code an app for the event. Neither of them is usable at this point. You know, it's for different reasons. Yeah. Yeah, recognizing speakers is a great idea. It's a good way of recognizing all the efforts that some of them have put in. I think it's always sort of a challenge putting the people on sort of that stick, right? How do you gauge it and collating feedback? Some of it is a bit subjective, but I agree, I think we need to do something that has good feedback. I think, I don't know, there's two students, two lady students who came in from Goat at AndroidCon and they're still here. They came over and there's the first time they're at AndroidCon, they enjoyed it. And one thing they both asked me is, why don't we have more women speakers? And I was like, I completely agree. I wish more of the women in the community were sort of coming forward. So I've reached out to a few, Bavia. So yeah, we're turning to you next year. So we're definitely looking for more women in the community to come forward. We definitely want to make it a platform where everyone can come forward and be a part of this, share your knowledge, share your learnings and feel welcome. Cool, so that's it for me. Guys, thank you so much for the feedback. I'll be honest that I'm not sure all of it is gonna happen next year, but we'll take all the feedback to heart, we'll run through it. We might follow up offline with some of you. We welcome more specifics and we'll try to figure out from there what we can take into account. We've got three days next year to play with, which is great news, Kiran. So a lot more time, a lot more sessions. I think it should be a lot more fun. Thank you all. I have a bunch of people to thank for helping make this event possible. And at the end of it, I remember there was a contest going on and somebody's won it. We'll find out who will end. First, I'd like to thank the sponsors. If it wasn't for sponsor support, we wouldn't actually be doing this event because it takes a lot of effort and a lot of resources to put together an event. So I want to thank the people who sponsored us. Intel, who's been our world sponsor, who's got prizes to announce. Follow on guys, I'm going to call you out for that later. Intuit, Yandex, these guys came all the way from Russia. It's a long trip to make just to spend two days talking to developers here. And I think they deserve recognition for that. They sort of spent a lot of time in the audience talking to people. And if you have been thinking of abstracts, try them out. I went to the talk yesterday. I don't know if many of you were there because I counted only about 25 people in the room. But I actually learned things about abstracts that I did not know before and I thought I knew everything about abstracts. So that was a great talk yesterday. Intuit, as I just mentioned. Little I and the sponsors for the Hack Night, Mobstack and Lookup, they haven't been part of the main event. They came to the Hack Night instead because they figured it was better to go to a focused audience over there. I think that was great. And I'm going to call out the team and all of the people who helped make this possible. I'm not going by alphabetical order. It's just random order. Grace, so not everyone is in the room right now. I'm just going to call out whoever is here. Please come up if you're in the room and standing here right now. Ashwin, Radha, Sajad, Kingsley, Francesca, Harris, Zainab, Prasita, Hasib, Pradeep, Sandeep, Anant, Anupam, Akshay, Nanu Prakash, Vishal, Anirudh, Sandeep, Anant, Chiti Potu, Vamsi, Anu, Siddharth, Ashwin, Vipul, Pratul, Naufal and Arvind and of course Kausab. The man who's been here all day. Yeah, I called Anu. Hey Anu, come in. Okay, somebody has got to take video. So there's Anu who's refusing to let go for duty of the camera on the backside. There's a power button, you have to press it twice. So thank you guys. As you can see, it takes a lot of people to pull together an event and everyone's got critical duties because even if one person is not doing their job, something or other starts going wrong. So who's got the mic? He's been running the event for the last several weeks. I don't know, it's just been two weeks. So yeah, I mean, thanks to all of you. The program committee, Arvind, Kingsley, Soham, Amrit, I don't know if they are here. Come on stage. Yeah, the Bangur Android user group. You know, you guys. No, no, the DroidCon program committee. Ravi, you should be up here too for the app. Ravi, we asked, weren't midnight oil and developed app app? Next year, you'll have an app for sure. The app is ready already. What we would need help is, it's already on GitHub, help us kind of put in more features and probably clean up the code. I gave you all that paneer that night you still didn't make the app. Okay, so yeah, thanks. I think Ravi, Amrit and Soham was just absolutely fantastic at the DroidCon hack night. And as you could have seen, we had three great app demos and six other apps. You can see the videos on YouTube. So thanks guys. I don't think we could have run the app without the three of you and all the chattering and patterning. So thank you so much. I guess you're in the volunteer team. I have a special thanks to Francesca who came in right towards the end who helped really manage all the people here and where's Norphal? Norphal who's been here in since the past two months coordinating the volunteers and getting people around. And thanks to all of you and to people downstairs who haven't shown up here. It seems like it's Monday into man a camera or to pass a mic around or to keep time for speakers. But these are things that actually make a conference so smooth because you want the sessions to run on time. You want the speaker's experience to be as good as the participant's experience. And as much as these things seem Monday, they cannot run without these things. So thank you guys. Some of you have been around with us through the course of this year. For some of you, this is your first event. I hope we'll see a lot more of you next year supporting us at the event. And yeah, I think that's all. Thanks so much. I forgot to mention one of the sponsors, MTS. I'm sorry guys, so thank you too. And finally, I think you guys can all get back and have an ice seat. The final bit, Intel's contest. There are two contests going on here. I know the details of one. I'm not sure of the details of the other. So I'd like the Intel guys to come up and talk about it and give away your prize. So one of them is a QR code contest. The other one was a photo contest. Thanks Kiran. Thanks. It was a great event. My first DroidCon. So thanks for awesome response. I have one of the contest winners named with me and rest of the contest winners I'm gonna get from XANAB. So before I announce the winners, I would like to thank Intel team. Amit, who is a technical marketing manager, I would like him to please come on the stage. Nitish, who's been doing some fantastic work on Android and on X86 platform. Nitish, please come on the stage. So first I wanna announce the name of a number of people who have won Android development board. So the first person, Amit, please come on. Nitish. The winner for the first contest, I'll just name the numbers. 4709, with a tag on there. You registered with that number, right? I'm sorry I don't have the names, I just have the numbers. 4709. The next one is 7523. Seems like we are playing housey. If you're not in the room, you're not getting a prize. This is why you have to stay. Okay, the next number is 1613. Nobody in the house? Somebody else lost a prize. Oh, there's one over there. Okay, excellent. And last in this category, 9504. So we have one person who's not here. So we have a few backup numbers. Excellent. Okay, so the backup number is 1161. Yay! So thank you guys, thank you for taking the contest. With the fourth one, we would need the numbers as well. 4709, 950. I'll take it. So what's your name? Rajiv Mishra. So thank you Rajiv, thank you for participating in the contest. The second is 7513. Okay, 1613. Okay, thank you. What's your name? Sushil. Sushil, thanks Sushil. The third is 9504. What's your name? Guru Teja. Guru Teja, thanks. I'll have this, yeah. And double 161. Vivek. So thanks guys, thanks for participating in the contest. We had two more contests. So one of the contest was to take a picture with the Android cutout. Okay. And the winner... So Francesca and I were entitled to look through the Twitter stream and figure out who took the best picture with the Intel Droid. Yeah, it's already there. Hey, Kostu, can you switch to the next tab? Yes. So there were about 20, 25 entries and this is the picture that we thought was interesting. And there's a Droid. It looks like the Droid's holding the camera and taking a picture. So, and that's Vipul. Vipul's been running around and taking pictures as well. So, and the picture was taken by Kingsley. That's what I knew. So Vipul's the winner. So Nithish, good to be with you in the honour. And there was one more contest called App Pitching Contest. Okay, so the winner of the App Jam Contest is Karan Rao. And his suggestion was for an app for people with disabilities. And that kind of was unanimously voted by me and Srikanth. And I think if you actually get to work on the app, it would be a great thing for a lot of people. For announcements that I forgot. I guess that's it. Then thanks guys. Thanks everyone for coming. This has been great. We'll, I hope we'll see you again next year. One last request. Please drop off your NFC cards when you go out. It'll save us some money because it's not cheap trying to buy new cards every month. So please, if you don't need your card, return it.