<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Android Makers backstage - Medium]]></title>
        <description><![CDATA[This publication contains all the article telling the story of organising Android Makers events - Medium]]></description>
        <link>https://medium.com/android-makers-backstage?source=rss----fa7af544e3ed---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Android Makers backstage - Medium</title>
            <link>https://medium.com/android-makers-backstage?source=rss----fa7af544e3ed---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:24:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/android-makers-backstage" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Android Makers 2025]]></title>
            <link>https://medium.com/android-makers-backstage/android-makers-2025-c1f7fef91988?source=rss----fa7af544e3ed---4</link>
            <guid isPermaLink="false">https://medium.com/p/c1f7fef91988</guid>
            <category><![CDATA[android]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[androidmakers]]></category>
            <dc:creator><![CDATA[Android Makers]]></dc:creator>
            <pubDate>Fri, 21 Mar 2025 13:20:09 GMT</pubDate>
            <atom:updated>2025-03-21T13:20:08.986Z</atom:updated>
            <content:encoded><![CDATA[<p>What to expect?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*714CEP5ooZhYc7vEZuRL-Q.jpeg" /></figure><p>Hello dear Android Community it’s been a while, a year. But with our beloved partner <a href="https://www.droidcon.com/">Droidcon</a> we are back with <a href="https://medium.com/u/810dec9385ed">Android Makers</a> stronger than ever.</p><p>We are so glad to see you all again at <a href="https://maps.app.goo.gl/j44k6rsdGFTANnWd9">Le beffroi</a> this 10–11 April.</p><p>Spoiler alert we have some new activity for you all so get ready for two intense day.</p><p>We still have 4 track of strong talks going on at the same time, on three format: Lightning talks, session and Workshops.</p><p>Both days are going to start with a keynote. We will start with the great <a href="https://medium.com/u/bf832913ceeb">Cyril Mottier</a> about “Building Scalable Mobile Projects: Fast Builds, High Reusability and Clear Ownership”. And on the second day we will be enlightned with <a href="https://medium.com/u/36866b664b0a">Xavier F. Gouchet</a> about “Being an ethical software engineer”.</p><h3>What will be the new stuff?</h3><p>If you haven’t yet checked the <a href="https://androidmakers.droidcon.com/agenda/">agenda</a> you might have noticed that we have reference 5 tracks. We had feedback about the upper room being a little bit too small sometimes so we will try to use one of the main floor room as a track room it gonna be called <em>Grand Salon.</em></p><p>And we will keep the 204 room, instead of having formal talk there you will be able to join a new format we named <strong>Unconference-Rountable</strong>. This format will allow you to join a discussion group to chat with other participant and share your thought about ongoing industry topics.</p><p>In this room there will be also Office hours where expert in their area will give time to answer all your question, so bring your problem there will be solutions there.</p><p>The app clinic will happen twice this year, once in french and once in english so we can enjoy it more.<br>There will also be a new collaborative workshop that will raise awareness about the environmental and social impacts of smartphones.</p><p>So if you are as hyped as we are don’t be late to the party and grab your ticket <a href="https://androidmakers.droidcon.com/tickets/">here</a> if you haven’t already.</p><p>And during the event don’t forget to have a stop at all our amazing sponsors (<a href="https://www.revenuecat.com/">Revenuecat</a>, <a href="https://www.happn.com/fr/">Happn</a>, <a href="https://www.zimperium.com/">Zimperium</a>, <a href="https://appvestor.com/">Appvestor</a>, <a href="https://www.moncoyote.com/fr/">Coyote</a>, <a href="https://kotzilla.io/">Kotzilla</a>, <a href="https://www.runway.team/">Runway</a>)that have prepared great activities for you. Thanks a lot to all of them.</p><p>Can’t wait to see you all 👋.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1f7fef91988" width="1" height="1" alt=""><hr><p><a href="https://medium.com/android-makers-backstage/android-makers-2025-c1f7fef91988">Android Makers 2025</a> was originally published in <a href="https://medium.com/android-makers-backstage">Android Makers backstage</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Better/faster: improving our video workflows for Android Makers 2019]]></title>
            <link>https://medium.com/android-makers-backstage/better-faster-improving-our-video-workflows-for-android-makers-2019-634ce40dce78?source=rss----fa7af544e3ed---4</link>
            <guid isPermaLink="false">https://medium.com/p/634ce40dce78</guid>
            <category><![CDATA[vidéo]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[androidmakers]]></category>
            <dc:creator><![CDATA[Djavan Bertrand]]></dc:creator>
            <pubDate>Mon, 24 Jun 2019 14:46:15 GMT</pubDate>
            <atom:updated>2019-06-21T11:29:59.807Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vzUWBE_iNbG0zN6D61QAIA.jpeg" /></figure><p>After each Android Makers event we ask to the participants the things they liked and the ones to improve for the next year. In the audience survey of 2018, the videos of the talks were on top of that list.</p><p>This article will explain what we did to improve the quality and the release time of the Android Makers 2019 videos.</p><h3>Last year review</h3><p>For us, the most important part in a video of a talk is the slides and the audio because this is where the content is. This is why, in Android Makers 2018 we tried to focus the camera on the screen rather than the speaker or the stage. This strategy was not as good as expected and this is why:</p><ul><li>filming a screen is not ideal as it can produce a flickering and annoying auto-exposure changes. Another problem is that the speaker was sometimes out of the filmed area.</li><li>the publishing time was not good enough: we publicly released the 70 videos of the 2018 edition more than a month after the event. This delay was due to the fact that we had to cut and re-encode every raw video. Indeed, when a video is recorded by the camera, the output video is split into multiple raw files. To have an exploitable video, we need to merge these files into one and then trim the video from the start to the end of the talk. The person in charge of producing the video and one person of the team did that “manually” for each video (more than 70 videos). After this step, we needed to add an introduction image that should fade into the video. After having the resulting video, we needed to upload it on Youtube and put the correct title, description, and thumbnail. Since we did not want to do that manually on every videos, we implemented a python script that runs an <em>ffmpeg</em> command to get the resulting video and to upload this video to Youtube with the correct metadata.</li></ul><p><a href="https://www.youtube.com/watch?v=8YDt2J7dHXA&amp;list=PLn7H9CUCuXAus0YgFW7QiIpnwHJd3Yinw&amp;index=16&amp;t=0s">Here is one of the worst example of the video quality</a> of Android Makers 2018, sorry Britt!</p><p>For these reasons, improving the Android Makers video process was one of our top priority for the 2019 edition.</p><h3>What we tried</h3><p>Months before the event, we brainstormed about what we could do to improve the content of the videos and to make them available quicker.</p><p>In order to improve the video quality, we wanted to have a video containing two parts: one big for the slides, the other, smaller, for the speaker.</p><p>The first solution we came up with was to launch a screen-record on the laptop of the speaker and to create a video containing the two parts in post production (i.e. after the talk is finished). Our friend (and member of the PAUG) <a href="https://twitter.com/g123k">Edouard Marquez</a> was using that solution for his Flutter meetups.</p><p>This process is quite long since we have to adjust the timing of the two sources. This was way too long to do it on more than 60 videos, so we considered to synchronise the two streams thanks to the audio (this tools has been slightly tested:<a href="https://github.com/bbc/audio-offset-finder"> https://github.com/bbc/audio-offset-finder</a>).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/350/0*pGKsfCJttKqG3QW0" /></figure><p>This solution was a bit too complicated, required to operate on the laptop of the speaker and had a lot of work to do after the conference.</p><h3>What we did</h3><p>To speed up the release process of the formerly described solution, we wanted to edit the video while it was recording. The main idea is to merge the camera stream and the slides stream (output from the speaker laptop) in a laptop that will produce the video.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rCJAT5cnnmgMk77v" /></figure><p>We met Philippe Sentenac who is used to produce videos of this type. He has been kind enough to share his setup and help us record the September meetup (<a href="https://www.youtube.com/watch?v=1SiuViLYurw">here is the video</a> of one of the talk). In the meantime, <a href="https://twitter.com/g123k">Edouard Marquez</a> started investigating a similar setup for the Flutter meetup and guided us through the hardware selection. Thanks to these experiences, we had a good grasp on the work to do to quickly produce quality videos. So a big thanks to Edouard and Philippe!</p><p>We decided to explore this solution and see how it would scale for Android Makers.</p><p>At Android Makers, rooms are very big so we can’t have a laptop connected to the speakers laptop while it is also connected to the camera. Luckily, in big rooms of the Android Makers venue, the control room is able to give us the stream that is projected on the screen. This way, slides and camera can be close enough to both connect them to one laptop that can record a video that merges these two streams.</p><p>For the smaller size rooms (10 meters long max), we should have a long enough cable from the speaker laptop to the recording laptop that is placed near the camera. As HDMI cables are limited in length, we opted for SDI cables that can accommodate longer distances.</p><p>Once the setup for each room has been defined, we could make our shopping list.</p><h3>The equipment list</h3><p>Let’s recap the technical setup of the Android Makers rooms:</p><ul><li>Two rooms with a control room that can provide a copy of the stream that is displayed on the screen, a camera and an audio stream that is plugged into the camera (i.e. the sound is merged to the video of the speaker by the camera)</li><li>Two smaller rooms with a camera filming the speaker and getting the audio, and a laptop far away (10 meters) providing the stream of the slides.</li></ul><p>Also note that the video producer will provide two camera that have an SDI output for the big rooms and two camera with a mini-hdmi output. The computers in charge of recording the video will be provided by organizers of the Paris Android User Group.</p><p>Here is the equipment we need:</p><p>For each big room, we need two videos converters (one for the camera, the other for the slides stream). For each small room, we need one hdmi splitter (input: hdmi from the speaker laptop, output: one hdmi to the screen/projector and another to the laptop that does the record) and two video converters (one for the camera, the other for the slides stream).</p><p>Here is our shopping list for one big room:</p><ul><li>1 <a href="https://www.avermedia.com/fr/product-detail/BU111">AverMedia ExtremeCap SDI</a> (SDI -&gt; USB-C)</li><li>1 <a href="https://www.blackmagicdesign.com/fr/products/ultrastudio">BlackMagic UltraStudio Mini Recorder</a> (HDMI/SDI -&gt; Thunderbolt 2)</li><li>1 <a href="https://www.decimator.com/Products/MiniConverters/MD-LX/MD-LX.html">Decimator MD-LX</a> (SDI/HDMI -&gt; SDI + HDMI)</li><li>3 hdmi cables</li><li>1 long SDI cable</li><li>1 small SDI cable</li></ul><p>As you can see, this whole list cost quite a lot for the 4 rooms. The budget of the video part in Android Makers has increased this year, but this should be considered as an investment. Moreover, the cost of the video production will be decreased since we will lower the post-production work.</p><p>On the software part, we will use <a href="https://obsproject.com/">OBS</a> to do the record.</p><p>Here is a schema of the setup for a small room:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p33veo6xUxa_sFAB" /></figure><p>We received the whole equipment one week before the event. We made two meetings to install the software, test the hardware, and understand how the overall setup works.</p><p>After these meetings, we shared with the team the OBS scenes to use on the D-Day. This json file describes the scenes that we can use and the output.</p><p>We decided to have 3 scenes.</p><ul><li>The main one shows the slides and the speaker at the same time. This scene has a white background that contains the Android Makers logo. On the top left is the speaker stream. This part is a cropped rectangle of the camera stream. And in the center are the slides.</li><li>A scene that only shows the slides, full screen.</li><li>A scene that only shows the speaker, full screen.</li></ul><p>This OBS setup is available <a href="https://github.com/paug/video-tools/tree/master/obs">on our Github</a>.</p><h3>The D-Day</h3><p>On the D-Day, we had one staff member dedicated to each room. This person was in charge of setting up the hardware, testing mics and audio gain, changing batteries when empty, changing the scene if needed… and of course, pressing the start/stop button !</p><h3>Publishing the videos</h3><p>After the event, we got back home with 66 videos. To release them, we re-used the scripts that we made last year, but with some modifications (and a Kotlin script implementation, yay). All these scripts are open-sourced: <a href="https://github.com/paug/video-tools">https://github.com/paug/video-tools</a>.</p><p>The first modification we did was to improve the ffmpeg command to adapt to new need we had this year. Hence we added a way to:</p><ul><li>trim the start and the end of the video</li><li>only use one audio channel and output it on both channels. This is because we kept two different audio sources on the camera on some rooms: one was the speakers mics, the other was the camera mic (as a fallback if the microphone of the speakers did not work). So we had to remove afterward the audio channel that was not useful.</li></ul><p>Second modification was due to the YouTube API quotas limitation. The YouTube Data API v3 now requires to be verified by Google to use the <em>auth/youtube</em> scope. As we did not have time to do it, we used the “unverified” free tier that only allows smaller quotas. With this reduced quota, we could not use the script to upload all videos anymore. This is why we uploaded manually the videos once they were generated. We slightly modified the script so it can be used to only update the metadata of a video and upload the thumbnail.</p><p>With this process, a video gets generated in around 13 minutes and uploaded in 10. This is how we could publish all the 66 Android Makers videos for 2019 in 13 days.</p><h3>Android Makers 2020 and beyond!</h3><p>We improved the overall video quality a lot this year! And we want to improve it even more next year.</p><ul><li>The speaker part of the video is not as sharp as we can expect. Moreover, the speaker is sometimes underexposed or overexposed and it changes according to the speaker slides. This is because the cameras were recording the whole stage and we were cropping this stream to only show the area where the speaker is. This choice makes the speaker part a rectangle of 200x400 in a 1920x1080 stream. The exposure problem is also due to the fact that we were filming the whole stage: the auto-exposure of the camera is computed on the speaker but also (and mainly) on her/his slides. We made the choice to film the whole stage because we wanted to have a fallback if the recording laptop would crash. Since it was our first time, we really wanted to assure our back. Since our solution seems to work, we can choose to drop this backup solution and zoom on the area where the speaker can be. This way, we could have a 1920x960 resolution and the auto-exposure would be computed only on the speaker.</li><li>Some videos are laggy. We had one recording computer per room, and each computer was different. We had a high spec MacBook Pro and some old MacBooks. It seems that the oldest MacBook could not handle the two 1080p input streams too long. For next year, we will try to either improve the input/output config in OBS or, if this does not fix the problem, come with computers with better specs.</li><li>The 13 days release were good, but we can still improve. We lost some time this year to get all the settings to correctly generate the video (the audio channel to keep, the start/stop time and some metadata such as the tags). Next year, we could prepare a proper file that can gather the data we need and fill it directly during the event.</li></ul><p>Overall, improving the videos was a lot of work… and a lot of fun! We never imagined we could learn so much about SDI/XLR/MIC/MKV and other weird acronyms, but we’re glad we did and we’re quite happy with the results. You can see for yourself on <a href="https://www.youtube.com/playlist?list=PLn7H9CUCuXAu5r4kT8RcK8B2GuBqMODX3">our Youtube page</a>.</p><p>Don’t hesitate to let us know what you think. Stay tuned for more improvements next year!!!</p><p>Thanks a lot to all the Android Makers team (especially <a href="https://twitter.com/martinbonnin">Martin</a> and <a href="https://twitter.com/Eyal_Lezmy">Eyal</a>) for their help on this article, and to <a href="https://twitter.com/Antoinedroid">Antoine</a> for his review. ❤️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=634ce40dce78" width="1" height="1" alt=""><hr><p><a href="https://medium.com/android-makers-backstage/better-faster-improving-our-video-workflows-for-android-makers-2019-634ce40dce78">Better/faster: improving our video workflows for Android Makers 2019</a> was originally published in <a href="https://medium.com/android-makers-backstage">Android Makers backstage</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android Makers 2019 Dessert Hunt, behind the scenes.]]></title>
            <link>https://medium.com/android-makers-backstage/android-makers-2019-dessert-hunt-behind-the-scenes-bde3b4c8b8dd?source=rss----fa7af544e3ed---4</link>
            <guid isPermaLink="false">https://medium.com/p/bde3b4c8b8dd</guid>
            <category><![CDATA[androiddev]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Martin Bonnin]]></dc:creator>
            <pubDate>Tue, 14 May 2019 11:50:49 GMT</pubDate>
            <atom:updated>2019-05-14T11:50:49.573Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XpPm5aWnMEP9ybR2w1nsUA.png" /></figure><p>At Android Makers, we like desserts… a lot!🍦🍩😋</p><p>When we realized the conference was taking place the day following Easter, we couldn’t resist the urge of organizing a small Dessert Hunt. We also love experimenting with new Android tech, so we did it using <a href="https://developers.google.com/ar/">ARCore</a>.</p><h3>Building the app</h3><p>The app is entirely on <a href="https://github.com/paug/AndroidMakersApp">github</a>. The dessert hunt code is in the <a href="https://github.com/paug/AndroidMakersApp/tree/aa6bcc3462db9af87d94a1f2269338bf9fc4d0c9/app/src/main/java/fr/paug/androidmakers/flash_droid">flash_droid directory</a>. It uses an ArFragment to detect the augmented images like in the <a href="https://github.com/google-ar/sceneform-android-sdk/tree/master/samples/augmentedimage">augmentedImage sample</a>.</p><p>The augmented images database is built offline using <a href="https://developers.google.com/ar/develop/c/augmented-images/arcoreimg">arcoreimg</a>. Then the ArFragment will give us a callback when an augmented image is detected:</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/750d993ec03c7165dd6538bf5e875d36/href">https://medium.com/media/750d993ec03c7165dd6538bf5e875d36/href</a></iframe><p>We then use a <a href="https://developers.google.com/ar/reference/java/sceneform/reference/com/google/ar/sceneform/rendering/ViewRenderable">ViewRenderable</a> to display the Thumbs up 👍👍. Worth noting is that any view can be displayed in the scene. It can also be animated/interacted with, which opens a lot of possibilities. Definitely something to dig more!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*1GE-FEqxjR6EY1JEKNuxSg.png" /></figure><p>The backend is a simple Firestore instance. Saving a scan is as simple as writing a map to Firestore. We saved the timestamp. Even though it’s not completely hacker proof, this allowed us to detect a few cheaters :).</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/85b39f50d9d49a9e7915b5430e7003e5/href">https://medium.com/media/85b39f50d9d49a9e7915b5430e7003e5/href</a></iframe><h3>Replacing the poster on the Beffroi</h3><p>That one didn’t work until the very last moment when we realized we needed to help arcoreimg by giving the size of the poster (it’s big!):</p><pre>//images.txt<br>montrouge|montrouge.png|8</pre><p>It went smoothly after that:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*1KdxzSJgX4JT_r3-aAprKg.png" /></figure><h3>Hiding the desserts</h3><p>The desserts were hidden the morning just before the conference in different locations:</p><ul><li>Cupcake: on the cloakroom desk</li><li>Donut: downstairs next to room Blin and the dolls exhibition</li><li>Eclair: in the corridor leading to room Blin</li><li>Froyo: in the stairs between the lobby and 1st floor</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*yJ9ijNuXHlyJtONDKY1eYQ.jpeg" /><figcaption>Froyo was the last one to be found despite being in plain sight</figcaption></figure><ul><li>Gingerbread: on the ceiling next to room 203</li><li>Honeycomb: next to the coffee machine on the 2nd floor</li><li>IceCreamSandwich: in the foyer-bar, next to Leboncoin</li><li>Jelly Bean: in the lobby, behind the plant on the left</li><li>KitKat: behind the curtain, next to Blablacar</li><li>Lollipop:1st floor, in front of Hiway, next to an extinguisher</li><li>Marshmallow: left side of the bar on the 1st floor</li><li>Nougat: behind the kakemono On the 1st Floor</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*l9bmC6WjcdouQefAhZbIPA.jpeg" /><figcaption>Nougat was behind a kakemono</figcaption></figure><p>Two of them were digital:</p><ul><li>Oreo: the now classic 7 taps on the app version</li><li>Pie: ask the Google Assistant!</li></ul><h3>The aftermath</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*kBiwU7yfPtGaJR0pxhZ7YQ.png" /></figure><p>Over the two days, there were:</p><ul><li>265 participants</li><li>899 desserts successfully scanned</li><li>34 participants found all 14 desserts</li></ul><p>The full data set is available in <a href="https://docs.google.com/spreadsheets/d/1CwTvh7xbiKPDr1-f5l-KuacW-wGp7LntHqTmMs2rqOM/edit#gid=1463112622">Google Sheets</a>. A few insights:</p><ul><li>Cupcake was one of the first and most found. It makes sense as it was hinted in the app.</li><li>Froyo was the last one to be found despite being quite visible in the stairs. Mostly because no one ever stopped there.</li><li>The first participant found the whole 14 desserts on Tuesday ~2pm.</li><li>24 participants finished their scanning in the last 2 hours. Some information sharing might have happened at that time :).</li><li>Some desserts were found during the party around ~11pm on Tuesday night. They were in the Google Assistant, no one broke into the beffroi!</li><li>Pie and Oreo were also found with difficulty. In the google assistant, scrolling right in the list of suggestions would hint at the dessert.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*ku9DE7eNoqdtEKpIIJi2EQ.png" /><figcaption>Ask about our easter eggs!</figcaption></figure><h3>Making a prize</h3><p>The prize (a 2 pound chocolate bugdroid), was entirely custom made using:</p><ul><li>a Droid Mega to serve as a model</li><li>food-safe silicon to make the mold</li><li>and a lot of Valhrona chocolate! 🍫🍫</li></ul><p>This was a long and involved process, especially tempering chocolate… That would require another post I’m afraid! Don’t hesitate to use the comments section if you feel like doing your own chocolate mold!</p><p>A few pictures:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*VXDJjVkDCfR9GXuvbV5Dfw.jpeg" /><figcaption>Bugdroid Mega before being covered in silicon</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*kaUj8ZRb18hStwDtERgXSw.jpeg" /><figcaption>Mold done</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/1*hL7epumBeePVUsGMDQmy_g.jpeg" /><figcaption>Chocolate incoming</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*PiJE3WeudkbrjFUHYz1ZJw.jpeg" /><figcaption>Easter Droid waiting for his new owner!</figcaption></figure><p>We hope you had as much fun looking for desserts as we did building the it! Congrats to all participants who founds the desserts!!</p><p>And bon appétit Maximilien ;)</p><p>See you next year!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bde3b4c8b8dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/android-makers-backstage/android-makers-2019-dessert-hunt-behind-the-scenes-bde3b4c8b8dd">Android Makers 2019 Dessert Hunt, behind the scenes.</a> was originally published in <a href="https://medium.com/android-makers-backstage">Android Makers backstage</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Selecting Speakers for Android Makers 2019]]></title>
            <link>https://medium.com/android-makers-backstage/selecting-speakers-for-android-makers-2019-b8a4012464d7?source=rss----fa7af544e3ed---4</link>
            <guid isPermaLink="false">https://medium.com/p/b8a4012464d7</guid>
            <category><![CDATA[androiddev]]></category>
            <category><![CDATA[speakers]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[android-app-development]]></category>
            <category><![CDATA[call-for-papers]]></category>
            <dc:creator><![CDATA[Android Makers]]></dc:creator>
            <pubDate>Mon, 29 Apr 2019 22:34:33 GMT</pubDate>
            <atom:updated>2019-03-25T22:30:23.848Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*okO5vmViJpLXIM4ovTWGBg.jpeg" /><figcaption>The Android Makers 2018 speakers</figcaption></figure><p>In order to be more transparent, the selection committee for Android Makers 2019 will explain the process behind how we built the agenda for our conference.</p><p>This post has been written by <a href="https://twitter.com/loutry">Marion Hayoun</a>, <a href="https://twitter.com/Djava7">Djavan Bertrand</a>, <a href="https://twitter.com/stan_kocken">Stan Kocken</a> and <a href="https://twitter.com/Eyal_Lezmy">Eyal Lezmy</a>. We also want to give a special thanks to <a href="https://twitter.com/mikewolfson">Mike Wolfson</a> for reviewing this article!</p><h3>The committee</h3><p>The committee is the group that decided which talks will be on the agenda. It is composed by 6 developers:</p><ul><li><a href="https://twitter.com/Djava7">Djavan Bertrand</a>, iOS developer at Tag Heuer</li><li><a href="https://twitter.com/loutry">Marion Hayoun</a>, Android developer at Canal+</li><li><a href="https://twitter.com/stan_kocken">Stan Kocken</a>, Android lead developer at Dashlane</li><li><a href="https://twitter.com/Eyal_Lezmy">Eyal Lezmy</a>, Android developer at Tag Heuer and Google Developer Expert</li><li><a href="https://twitter.com/Nilhcem">Gautier Mechling</a>, Android developer at Innovorder and Google Developer Expert</li><li><a href="https://twitter.com/n0tnull">Adrien Vitti</a>, Android developer at Smart&amp;Soft</li></ul><p>Most of the committee are organizers of the Paris Android User Group. The event is co-organized with BeMyApp.</p><h4>The role of the committee</h4><p>The mission of this group was to:</p><ul><li>ensure interesting topics</li><li>keep quality high</li><li>ensure a variety of topics</li><li>keep the level of the talks properly adapted to the audience;</li><li>encourage inclusion and diversity</li></ul><p>We tried to forecast the trending topics so that our audience would be well prepared for them. We sometimes have hints that a given technology/product will be soon deprecated. In this case, we avoided selecting talks about that subject. If we think that a technology will be growing, we tried to get more content about that.</p><h3>Part 1: Call For Papers</h3><p>How did we get so many great speakers for a 2 days conference?</p><p>First, we opened a “call for paper” (CFP) website. This is a place where speakers from all over the world, from any background, could propose a talk. This website was open for many weeks and received 253 talks proposals from over 200 different speakers.</p><p>While the CFP was open, the organization team promoted it on social networks. The committee was also in charge of recruiting key speakers, which is a long-running task for some speakers. Organizers regularly solicit throughout the year getting speakers interested in supporting the event.</p><p>In the CFP, each speaker filled their profile with information about their company, speaking experience, and social media. This helped us evaluate their experience.</p><p>Each proposal also included: a title, a public description, a private message for the committee, the speech format (length of the talk, or if it is a workshop) and language (French or English).</p><p>The following chart shows the received proposals over time. You can see, this year we received a lot of proposals right before the CFP closed.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ck5kg4PJmfpD8cowOUSZiw.png" /></figure><h3>Part 2: Ranking the entries</h3><p>During the CFP, each member of the committee reviewed each of the talks independently. It can take up to 30 minutes per talk, and sometimes we had to ask the speaker for more information to evaluate a proposal correctly, which took even more time. The output of this review was a score for each talk. We rated each talk (from 1 to 10), which was used later during the selection.</p><p>During this process, we considered different aspects of every talk. The criteria were:</p><h4>Subject</h4><p>We evaluated the relevance of the topic. We asked ourselves:<em> Is this topic new or is it something already covered? Is it going to interest enough people?</em></p><p>For example “Getting started with Kotlin” is a topic that has been covered a lot recently. There is a limited value of this topic unless it’s discussed from a different angle.</p><h4>Description</h4><p>The abstract describing the talk will be published later in the schedule. We asked ourselves: <em>Does this description have enough info to explain the content provided during the talk?</em> <em>What will be the take away for the attendees?</em> <em>How will the speaker cover this topic?</em></p><p>To let the speaker give more details, there a “Message for the committee” section where they could give an outline, provide a link to the talk’s slides, or include any other information proving the value of the proposal.</p><h4>Speaker</h4><p>To evaluate the speaker we asked: <em>What is their experience? What is their expertise on this topic? Do they have any previous talks we can review?</em></p><p>Having experience as a speaker is a plus, but we did refuse some very qualified speakers based on the topic. We did accept some in-experienced speakers that had other examples of their expertise on the subject (like a tech blog post, or professional experience).</p><h4>Conflict of interest</h4><p>A committee member can decide if they are not able to rate a proposal impartially. This can happen if the speaker is working for the same company, if the topic conflicts with a talk that they have proposed, or any other reason they feel. In this case, the member won’t vote for the proposal or be part of the debate about it.</p><h3>Part 3: The selection</h3><h4>Picking up the winners</h4><p>Once the CFP had been closed, each talk is reviewed by each member of the committee.</p><p>Then we start organizing the selection nights. The members will gather and discuss the line-up for the conference. For the AM19, we met twice, and each session was over 5 hours.</p><p>To prepare these meetings we compute the available slots, to know how many talks we could fit within our agenda. This year there were 130 slots. A slot is 25 minutes long, so a regular 40 minutes talk would take 2 slots, and a 3 hours workshop would take 7.</p><p>This year we started by reviewing the talks with the largest standard deviation between ratings of the members. We debated about them and made sure we all understood the proposals the same way. The members could change their rating based on this discussion.</p><p>Now we were ready to pick our first talk!</p><p>We sorted all the talks by average rating. For the highest rating, we debated the talk, looked for similar proposals, and other talks by the same author. If we decided to go with this one, we added it to a list of “pending acceptance” and declined all the others from this speaker and the others with conflicting content. We kept the second best talk on a topic as a backup, in case the first speaker needed to cancel.</p><p>Then we checked the next highest ranked proposal, and continue the process.</p><p>We tried to have only one talk on a specific topic and one talk per speaker. There are very few exceptions to this basic rule.</p><p>This process took a long time (two full evenings for a total of 10 hours). When we had enough talks for the conference, we started sending approvals to the first wave of speakers. We used this to adjust our overall consistency based on the first responses we receive.</p><p>We are an international conference and we aim to have most of our talks in English. But, because we are in France we keep some slots in French. We had 4 rooms, so decided to keep at least one talk in French for each time slot. (approximately 25% French, 75% English).</p><p>We used this format to display the CFPs during the selection process:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qrmakY47fsX5HPzTpnIwGQ.jpeg" /></figure><p>When a talk was refused or accepted, the email was not directly sent to the speaker, because we sent the emails by waves.</p><h4>Sponsoring the speakers</h4><p>Some speakers required help with travel and accommodations. Our conference is not expensive compared to many others on the same scale, which doesn’t allow us to pay for every speaker, but we did have a limited budget some based on need. When we selected talks, we took this into consideration but we rarely refused a talk only because of this.</p><p>Some speakers asked for help after they’ve been selected, which was hard for us as we already allocated our budget to the speakers who requested it as part of their proposal.</p><p>None of our speakers were paid by the conference organizers, which is why we are extremely grateful for the donation of their time and effort. We couldn’t do this conference without them.</p><p>Some of our talks were “sponsored”. That means a few companies paid to have an employee selected to speak. We had 4 sponsored talks on our agenda (out of 69 talks). In this case, we worked with the company and the speakers to find the best talk quality to ensure these were as good as the other talks on our schedule.</p><h4>The Heartbreaker</h4><p>Selecting the speakers is hard!</p><p>We had 253 proposals for the 69 spots. This means a talk had a less than 30% chance of being selected.</p><p>With such a “small” amount of slots to fill, the committee had to eliminate a significant number of very good proposals. It was very frustrating for the whole team to refuse some valuable content. If your proposal was refused, don’t feel bad about your content or skills.</p><p>Every year, a few refused speakers ask why their proposals weren’t selected. We provided constructive and transparent feedback to all of them.</p><h3>Part 4: The Agenda</h3><p>Once we received acceptance from a speaker, we started to build the agenda. For each talk, we evaluated the potential audience, room size and chronology of similar topics (an introduction talk must happen before an expert version for example).</p><p>A couple of weeks after the end of the CFP, we shared the first version of the agenda. It could still change, but the attendees could start to get an idea about what the conference will look like.</p><h3>Conclusion</h3><p>To conclude, we wanted to share that we are incredibly proud of the quality of all the proposals we received. We could have accepted more than 90% of them, but we only had room for 27% of them. It doesn’t mean your talk was not good if it wasn’t selected, just that some other proposals were a better fit with our requirements and our constraints.</p><p>This year we are very proud of the result. This is not only due to our work but is thanks to the huge community of speakers who submitted amazing content.</p><p>For that, we want to thank you from the bottom of our hearts.</p><p>See you at Android Makers 2019!</p><p><strong>Update:</strong> After publishing this article we received feedback and wanted to bring some clarification on the “encourage inclusion and diversity”.</p><p>We have <strong><em>never</em></strong> selected a talk based on the ethnicity or gender of a speaker.</p><p>We encourage inclusion and diversity by reaching out to valuable speaker to submit a talk before the CFP closing date. Our role is to increase the number of proposals from groups that are underrepresented in the dev industry to increase the chance of having diversity in the lineup.</p><p>Indeed, from our experience, once the CFP is closed and the selection is starting, the die is cast. At this point the chance to be selected for any speaker will be the same. If we had ever decided to lower our requirement to select more people from an underrepresented group, then it would have shown and harmed our community in the long run.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8a4012464d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/android-makers-backstage/selecting-speakers-for-android-makers-2019-b8a4012464d7">Selecting Speakers for Android Makers 2019</a> was originally published in <a href="https://medium.com/android-makers-backstage">Android Makers backstage</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>