Create native Android and iOS apps that share up to 100% code
Apply for junior mobile development positions (Android and iOS)
Increased career options as a Multiplatform developer
Learning Xamarin opens up opportunities to build Windows Desktop, Windows Store, Mac, and even smart watch apps that share the logic of your iOS and Android app
Neither We have talked about what something is and how it can help you build Android and iOS applications that share C-Sharp code. Let's talk about the advantages of using it and why you should be using it merely a summary will allow you to be way more efficient when developing mobile applications. And during this lecture we're going to take a look at two scenarios that will help you understand that to start with better how it is that summary will allow you to be more efficient when developing mobile apps. So let's take a look at the first scenario. The First there is traditional app development. What we were seeing as one team developing the Android app and another developing the iOS app first. Well it means that you have to have one team per platform. You have to have one team for developing the Android app in one team for developing the iOS app. This also means that each team is an expert on their platforms. So maybe I use developers won't be able to help the Android developers. Neither the other way around in case it's needed. And this also applies when it comes to individuals. I have come across a lot of people who are individuals who want to build an Android and iOS that but it's just too difficult or too time consuming for them to learn two languages two platforms. There's also the fact that teams work at different speeds. It's just inevitable when you have one team working on the Android app and one team working on the iOS app there is always one team that is going to be moving faster than the other. And this creates a lot of complications both internally and externally internally is going to be harder to implement new features if one team is still lagging behind and externally it's going to make users angry because they see that some of the people they know have this feature on the same app but in a different platform and that they still don't have it. They are just going to be frustrated by seeing that the same app is actually different from one platform to another. For this new app development also takes more time even when it comes to two teams even if those two teams were working hand by hand and delivering the same day. It just takes more time because it takes more people and you are taking the time of each and every one of the members of the team. So you are taking time from two teams because of the same reason traditional app development also consumes more money. Now let's take a look at something. AB devolvement with seven of development. You only need one team. One team can build the Android and iOS app. Problem solved. This also means that everyone in the team knows the same thing because they are building for the same platform so they can help each other and in the case of the independent developer. Well now they only need to learn one language one platform and be able to deploy to more than one app store by having only one team. This also means simultaneous development. So the same features are always available in the platforms that are being supported and for the same reasons because it is only one team. It takes less time. You're only using the time of one team because it is only one team that is simultaneously developing two apps. It consumes less money. You also find that it is very likely that when you start developing with some rain you won't be starting from scratch. So if you have some previews mobile app development experience chances are you're not going to be starting from scratch. For example if you have developed Android apps you will find that using something Android is going to be almost identical. The only difference really is that you're not going to be using Java but C-Sharp pretty good structure and the overall way the project works is going to be very similar and the same applies to us if you have previous experience that a whopping Irus project you will see the structure and the way you define the user interface and the way you code events for example is going to be fairly similar. And if you have experience developing we new Sapps whether it's for mobile or for Desta several anti-Sharia are going to make you feel right at home when they're helping semi-informed applications. And finally something that we haven't already covered in the previous lecture you end up with native applications. That's right. You end up with an application that uses native user interfaces that uses native API. And because of this has made it performance so your users will actually enjoy the application better. If it were for example an HMO or five application. So now though we've talked about some of the benefits of using some rain in the next lecture we're going to compare the two different versions of the song platform. Native versus summering forms.