It depends what you consider developer-friendly, and what you're developing obviously. Windows is certainly inferior for backend development, but I prefer it to OSX for writing for Android. Tooling is about the same, OSX being Unix-based doesn't really matter, and Windows UX simply feels more reasonable to me.

I'm usually sceptical about "fancy" CVs, but this is fresh and quite funny :) well maybe putting "knowledge" as a hobby is a bit pompous, but whatever. Interestingly, my path was quite similar - born in 1981, programming a lot as a kid; for a few years I even co-authored a series of articles with my teacher for a nationwide IT magazine in my country. Back in the day it was Turbo Pascal / Visual Basic / Delphi. And later on I "wandered" just like that guy... majored in politics, worked in fast foods, hypermarkets etc. before I finally dusted off the old hobby and turned it into a profession :)

Follow-up on #1: http://android-developers.blogspot.com/2016/05/android-studio-22-preview-new-ui.html This week at Google I/O 2016 we launched Android Studio 2.2 Preview. (....) This preview includes the following new categories of features: Design Layout Editor: A new user interface designer that helps you visually design the layouts in your app. Features like blueprint mode and the new properties panel allow you to quickly edit layouts and widgets faster. Constraint Layout: A new powerful and flexible Android layout that allows you to express complex UIs without nesting multiple layouts. Layout Inspector: Debug a snapshot of your app layout running on the Android Emulator or device. Inspect the view hierarchy and corresponding attributes. So they're trying to improve things in this area

It appears very interesting, I wish I could attend. It seems like plenty of material for a short talk though. How much time will you have? I don't know how you plan to cover Hapi.js and Mongoose, but please bear in mind that most Android developers aren't full stack devs. The majority wouldn't probably have any backend experience to speak of. So my advice would be to make sure not to lose your audience at this point, especially since it will have to be a rather highly paced talk

Ad 1. In general terms, Android Studio is as good an IDE as it gets. As for working with pure code, I believe it beats everything else I've heard of. As a UI designer though, it's still lacking, and no, there's no better alternative in sight. Speaking of third party libraries, there's plenty of them, but picking one is still a game of hit and miss. You never know if the library will meet all your requirements. For instance, lists. Android SDK still doesn't support things like sticky headers, or reordering by drag&dropping... (Not out of the box, I mean) Ad 2. Of course there are, however I wouldn't say memory leaks have a significant impact on development time, of all things. What's really tough and definitely slows developers down is Android's mind-boggling lifecycle model. It's brittle and bug-prone. Its complexity can also lead to memory leaks, but this is only one problem among many. Ad 3. I would take their statistics with a grain of salt - it's a sample not big enough to be truly representative, much less conclusive - but I believe they're correct in general. Android SDK is somewhat more difficult to work with. Fragmentation is definitely a big issue as well - Android devs don't have just a few devices to care about, but an endless variety of models, screen sizes, Android distributions (yes, every major manufacturer tweaks the OS a little) etc.

Android devs already have Kotlin at their disposal - which, by the way, happens to be uncannily similar to Swift , syntactically at least. It already has a small but loyal following, it offers 100% Java interoperability, it's backed up by JetBrains, so it's seamlessly supported by IntelliJ Idea / Android Studio, it's been highly regarded by quite a few influential figures in Android development world. And it's not controlled by Google's most serious competitor (in mobile, of course); open-source or not, this could be a liability. And at any rate, as far as I can tell, Google adopting Swift is merely a rumour at this point. For reasons given above, I'd rather see Google give an official blessing to Kotlin.

PhoneGap and Appcelerator fall under the Hybrid category, I think. The big absent one is Xamarin, which - like React Native - is a cross-platform solution that does produce native apps, so kind of best of the both worlds.