3 sins of mobile development at Mobius 2016
There are 3 days left until Mobius 2016, and the program is ready. It turned out 24 reports on mobile development: Android, iOS and cross-platform. To carefully study them all, you need to spend almost an hour of time, so we prepared a small guide on the program, which itself divided into three areas, not tied to the platform:
However, this post is not only about the conference - each of the reports falls into the program because of one or another “sin” that is common among programmers. Let's see more ...
')
Yes, this is the eternal expectation of new versions of our favorite tools, frameworks, technical solutions or even development approaches. Silver bullet syndrome in programmers in the blood, and, obviously, is transmitted by airborne droplets.
True, new versions of iOS bring not only pleasant surprises, but the deadline will not wait for Java 9 on Android (and we are waiting for something like this) - we need to work here and now. The truth is that we already have a full clip, albeit not silver, but deadly effective cartridges, and it was to them that we decided to devote the lion's share of our reports: why wait, when everything is ready? Take and write code.
It will be better, you say? And you will be absolutely right! However, even now we have the tools for those who crave for safe, reusable and maintainable code in iOS development, a direct route to Swift - using the example of generics and Application Coordinators, we will consider the tools of iOS developers that are not used in new projects due to the fact that it simply was not in Objective-C or not much is said about it. A detailed interview about what buns and rakes laid out in Swift, can be read here .
The same goes for Android: only the main problem of the platform is its fragmentation. And Google has rolled out its solution a long time ago in the form of the concept of Material Design - a set of approaches that give us the opportunity to make a beautiful, lively application without being a genius in design. What does the developer have to do with this? Given that 77 percent of applications get bad marks due to the fact that they look terrible, regardless of the optimization, the correct backend or wide functionality. How to cope with this, tell Wiebe Elsinga (Android GDE / UX Expert) and Vladimir Ivanov, who in practice implements Material Design into their applications. By the way, you can read a great interview on this topic here .
We will also talk about current (and most importantly, already working!) Frameworks:
Egor Tolstoy (Rambler & Co) will tell about Typhoon ;
Igor Vasilenko (Yota) - about ReactiveCocoa ;
Kirill Popov (Odnoklassniki) - about when ready-made libraries are better than their native “bikes” on the example of Fresco ;
Denis Kretov and Maxim Evtukh (Notissimus) - how they managed to reduce development time for several platforms using Xamarin and MvvmCross .
There are at least 2 types of developers: those who like to build high-level architectural "castles in the air" and those who bury themselves for the most "do not want" in the jungle of low-level optimizations. The first type programmers often forget that not only driver developers should understand low-level nuances: you should always understand how your code will behave on a particular platform, on a particular VM. And this is a very common "cant", although among the participants of our conferences there are many developers of the second type: those who like to work closer to the OS. Among the speakers, too - this time we have a quarter of the reports under the label "hardcore": about the "guts", virtual machines, languages ​​and programming approaches.
Two reports, one for each platform, are allocated to the reactive approach: Matvey Malkov already did an “introductory report” about reactive Android for Android last year , this time it’s about the mistakes that developers make and what is the correct reactive Android programming (by the way, there is a recent interview on this subject). In iOS, Yevgeny Rtishchev (Sberbank-Technology) will tell about the reactive approach in the report “Reactive MVVM”
We talked about Swift in the last section, since there’s not much of a move in the iOS world. But from the point of view of the choice of available development languages, Android provides an extensive “menu”: in addition to Java 7 and 8 (in the foreseeable future), applications written in Kotlin and Scala go into sales. About the pros and cons of mobile development in these languages ​​will tell Jan Zhulanov (JetBrains) and Matvey Malkov (for more than a year, writing on Scala) .
Well, the last two reports in this category are devoted to Android internals: Dmitry Polishchuk's report on the subtleties and rakes in working with the Android multimedia subsystem and Mikhail Rozumyansky's presentation “Bytecode weaving 101” , in which bytecode code generation is given, bytecode patching in general and advantages and disadvantages compared with standard annotation processing.
“What nonsense? The first point is about silver bullets, and the third is about conservatism? ”Yes, that’s right! We are waiting for some decisions, we study them with enthusiasm and joy, but all this works only where we are interested . However, the fate of any developer is full of surprises: all the time there are a lot of changes that have to be studied. And no one wants that .
However, the technological stack of the mobile developer is updated even faster: Material Design, Swift 3.0, React, Kotlin, new versions of virtual machines and operating systems - just manage to watch and master: all this takes time and effort. At Mobius, we have prepared for you a squeeze of important news so that you do not spend dozens of hours surfing the Internet and trying to filter out useful things from tons of information "noise".
The simplest example: Google i / o 2016 - hundreds of disparate articles and announcements, one repeats the other, and the third distorts the second - while most of this is designed for geeks and sympathizers. To be honest, we never managed to find a single source with all the important information for the programmer from the conference, so personally I would be happy to listen to the report with the “hot news” for developers . from the mouth of Denis Neklyudov, Android GDE. And as a seed, you can read an interview with Denis about Android N.
The second example: it is very difficult to assess the prospects of certain technologies independently. After all, we all believed in the success of Google Glass, and where are they now? On the other hand, the VR or Android theme of off-the-phones is growing and evolving , becoming an industry. Is it time to move in this direction? This will be a couple of reports:
The third topic you should know, but which you don’t really want to delve into, is security: Boris Ryutin will tell you about the latest iOS and Android features in this area .
Of course, an inquisitive reader, having come to this line, having considered the reports in the program and in the article, will find that the checksum has not converged. Yes, because in fact there are four sins, and in the last sin many people do not want to admit to themselves:
Yes, no one likes coding - everyone loves to solve interesting problems and puzzle over algorithmic problems or optimization. And who will write? In any case, on Mobius we have several reports on writing test code , on practical “acceleration” of your applications , on fast management of a set of “features” and their configurations , and also on practical typography in iOS .
There will be no indulgences, but for every sin we have something to say. If you know something that is worth talking about at the conference, but there is no such thing in the program - feel free to contact us, next time we will try to do everything at the highest level.
See you at the conference!
PS if you want to Mobius, but do not get to St. Petersburg, we have an online broadcast .
PPS If you want to look at the reports of past Mobius, they are already all posted on our YouTube channel .
- On the Edge;
- Hardcore;
- Software Craftsmanship;
However, this post is not only about the conference - each of the reports falls into the program because of one or another “sin” that is common among programmers. Let's see more ...
Sin 0: Adoration of silver bullet.
')
Yes, this is the eternal expectation of new versions of our favorite tools, frameworks, technical solutions or even development approaches. Silver bullet syndrome in programmers in the blood, and, obviously, is transmitted by airborne droplets.
True, new versions of iOS bring not only pleasant surprises, but the deadline will not wait for Java 9 on Android (and we are waiting for something like this) - we need to work here and now. The truth is that we already have a full clip, albeit not silver, but deadly effective cartridges, and it was to them that we decided to devote the lion's share of our reports: why wait, when everything is ready? Take and write code.
It will be better, you say? And you will be absolutely right! However, even now we have the tools for those who crave for safe, reusable and maintainable code in iOS development, a direct route to Swift - using the example of generics and Application Coordinators, we will consider the tools of iOS developers that are not used in new projects due to the fact that it simply was not in Objective-C or not much is said about it. A detailed interview about what buns and rakes laid out in Swift, can be read here .
The same goes for Android: only the main problem of the platform is its fragmentation. And Google has rolled out its solution a long time ago in the form of the concept of Material Design - a set of approaches that give us the opportunity to make a beautiful, lively application without being a genius in design. What does the developer have to do with this? Given that 77 percent of applications get bad marks due to the fact that they look terrible, regardless of the optimization, the correct backend or wide functionality. How to cope with this, tell Wiebe Elsinga (Android GDE / UX Expert) and Vladimir Ivanov, who in practice implements Material Design into their applications. By the way, you can read a great interview on this topic here .
We will also talk about current (and most importantly, already working!) Frameworks:
Egor Tolstoy (Rambler & Co) will tell about Typhoon ;
Igor Vasilenko (Yota) - about ReactiveCocoa ;
Kirill Popov (Odnoklassniki) - about when ready-made libraries are better than their native “bikes” on the example of Fresco ;
Denis Kretov and Maxim Evtukh (Notissimus) - how they managed to reduce development time for several platforms using Xamarin and MvvmCross .
Sin 1: Knowledge of "high level".
There are at least 2 types of developers: those who like to build high-level architectural "castles in the air" and those who bury themselves for the most "do not want" in the jungle of low-level optimizations. The first type programmers often forget that not only driver developers should understand low-level nuances: you should always understand how your code will behave on a particular platform, on a particular VM. And this is a very common "cant", although among the participants of our conferences there are many developers of the second type: those who like to work closer to the OS. Among the speakers, too - this time we have a quarter of the reports under the label "hardcore": about the "guts", virtual machines, languages ​​and programming approaches.
Two reports, one for each platform, are allocated to the reactive approach: Matvey Malkov already did an “introductory report” about reactive Android for Android last year , this time it’s about the mistakes that developers make and what is the correct reactive Android programming (by the way, there is a recent interview on this subject). In iOS, Yevgeny Rtishchev (Sberbank-Technology) will tell about the reactive approach in the report “Reactive MVVM”
We talked about Swift in the last section, since there’s not much of a move in the iOS world. But from the point of view of the choice of available development languages, Android provides an extensive “menu”: in addition to Java 7 and 8 (in the foreseeable future), applications written in Kotlin and Scala go into sales. About the pros and cons of mobile development in these languages ​​will tell Jan Zhulanov (JetBrains) and Matvey Malkov (for more than a year, writing on Scala) .
Well, the last two reports in this category are devoted to Android internals: Dmitry Polishchuk's report on the subtleties and rakes in working with the Android multimedia subsystem and Mikhail Rozumyansky's presentation “Bytecode weaving 101” , in which bytecode code generation is given, bytecode patching in general and advantages and disadvantages compared with standard annotation processing.
Sin 2: Laziness and conservatism.
“What nonsense? The first point is about silver bullets, and the third is about conservatism? ”Yes, that’s right! We are waiting for some decisions, we study them with enthusiasm and joy, but all this works only where we are interested . However, the fate of any developer is full of surprises: all the time there are a lot of changes that have to be studied. And no one wants that .
However, the technological stack of the mobile developer is updated even faster: Material Design, Swift 3.0, React, Kotlin, new versions of virtual machines and operating systems - just manage to watch and master: all this takes time and effort. At Mobius, we have prepared for you a squeeze of important news so that you do not spend dozens of hours surfing the Internet and trying to filter out useful things from tons of information "noise".
The simplest example: Google i / o 2016 - hundreds of disparate articles and announcements, one repeats the other, and the third distorts the second - while most of this is designed for geeks and sympathizers. To be honest, we never managed to find a single source with all the important information for the programmer from the conference, so personally I would be happy to listen to the report with the “hot news” for developers . from the mouth of Denis Neklyudov, Android GDE. And as a seed, you can read an interview with Denis about Android N.
The second example: it is very difficult to assess the prospects of certain technologies independently. After all, we all believed in the success of Google Glass, and where are they now? On the other hand, the VR or Android theme of off-the-phones is growing and evolving , becoming an industry. Is it time to move in this direction? This will be a couple of reports:
- Korshak Alexander on the practical application and development for Cardboard
- Alexey Rybakov about Android TV Gaming (Vulkan API, Nvidia Gameworks, etc.)
The third topic you should know, but which you don’t really want to delve into, is security: Boris Ryutin will tell you about the latest iOS and Android features in this area .
Of course, an inquisitive reader, having come to this line, having considered the reports in the program and in the article, will find that the checksum has not converged. Yes, because in fact there are four sins, and in the last sin many people do not want to admit to themselves:
Sin 3: No one likes to code.
Yes, no one likes coding - everyone loves to solve interesting problems and puzzle over algorithmic problems or optimization. And who will write? In any case, on Mobius we have several reports on writing test code , on practical “acceleration” of your applications , on fast management of a set of “features” and their configurations , and also on practical typography in iOS .
What is the result?
There will be no indulgences, but for every sin we have something to say. If you know something that is worth talking about at the conference, but there is no such thing in the program - feel free to contact us, next time we will try to do everything at the highest level.
See you at the conference!
PS if you want to Mobius, but do not get to St. Petersburg, we have an online broadcast .
PPS If you want to look at the reports of past Mobius, they are already all posted on our YouTube channel .
Source: https://habr.com/ru/post/302400/
All Articles