Introduccion a xamarin

Notas del editor

• #4: Xamarin is your complete mobile solution. Xamarin Platform is usually what you hear about which is building native iOS, Android, Mac, and Windows Apps all in C# However Xamarin offers a wide range of products for developers to go mobile including Test Cloud, Insights, and a way to learn all of mobile with University.
• #5: What makes up a “Native” mobile application? I am sure you have heard the “native” thrown around, but what does that really mean?
• #6: A native app needs a lot of things, but three important ones stick out: Native User Interface: Apps need to look and act correct per platform. Full SDK Access: As a developer we need to add the latest and greatest features Native Performance: Needs to be fast and fluid
• #7: So we know what we want how do we get there? Let’s talk about the state of mobile development.
• #8: Varios equipos Varios origenes de código Caro y lento Positivo = se entregan buenas apps a los usuarios de las plataformas Negativo= Desarrollo obstaculizado por múltiples bases de código y la fragmentación
• #9: Usuarios infelices Desarrolladores infelices Aumento en las apps abandonadas Limitado en lo que se puede implementar
• #10: UI native por plataformas, aprovechando C# C# + XAML C# + XML C# + XIB Una base de lógica compartida, iOS, Android, Mac, Windows Phone, Windows Store, Windows
• #11: Xamarin recently introduced Xamarin.Forms a new library for cross platform user interface. We will touch up on this later, but this enables you to be highly productive, share code, but build out UI on each platform and access platform APIs. With Xamarin.Forms you now have a nice Shared UI Code layer, but still access to platform APIs You can start from native, pick a few screens, or start with forms, and replace with native later
• #12: With Xamarin it just isn’t your front end in C# it is your full backend server as well. With Azure or even on Linux running Mono or the CoreCLR your app is fully C# end to end!
• #13: Let’s talk a bit about C# and why it is awesome.
• #15: Use your favorite libraries like Json.NET!
• #16: Here is an example of creating a class with a method to get names 1 Line with LINQ to execute this command Take advantage of C# features and set properties easily
• #17: The async and await keywords in C# 5.0 now available to Xamarin developers make asynchronous programming incredibly pleasant. You end up with code that is much more linear and much easier to understand. The compiler does a lot of magic for you which simplifies your code and your life.
• #18: With Xamarin we even extend native methods with C# Features Here there is no need for a callback block, simply await on the animation to finish before continuing on
• #19: Here we can see how easy it is just to do a += for an event and not have to implement a bunch of listeners every time. Easy to read, string.Format, using args, etc. In fact we can make this call Async/Await by just adding async to the delegate!
• #23: Major announcement at the end of 2013: Truly Portable Class Libraries Support for VS 2013 Special offers for MSDN Subscribers 20 City Roadshow! Another partnership at the end of 2014: Support for VS 2015 + Community Edition Special MSDN Offers Starter Edition Support for Visual Studio
• #24: IBM MobileFirst SDK for Xamarin: A pre-built software library that Xamarin and IBM developers can embed in their mobile apps to connect, secure and manage the apps using IBM Worklight, a part of the IBM MobileFirst portfolio. IBM MobileFirst Add-Ons for Xamarin Studio and Visual Studio: Extensions that enable developers to configure and access the IBM Worklight server from a single environment.
• #27: If you have ever developed for a Windows Platform before these .NET namespaces might look familiar. However, if we go to a new platform such as Windows Phone or Store we have a new SDK to use and a new set of namespaces.
• #28: You can think of iOS and Android development the same with Xamarin. You can see we have all of our .NET namespaces and libraries, but Xamarin give us 100% api coverage of each iOS API in it’s SDK that we access view C#.
• #29: The same is true for Android as well.
• #31: There is no compromise on performance. Xamarin apps look and feel native because they are native.
• #32: Apple has a developer preview where Xamarin has alphas ready. Google does not offer this. Android versions are usually 4 to 8 weeks out for a stable release, but alphas and betas are usually earlier. Xamarin realizes how important having iOS ready because within 24 hours a large portion of iOS users upgrade Android on the other hand is much different. After 4 months on the market Android 4.4 only had 1% adoption
• #35: Use all of your favorite libraries from NuGet or share and distribute your own!
• #37: iCircuit is made by Frank Krueger, a long time Mono & Xamarin developer. Sharing code lead to 70 to 90% code reuse across platforms speeding up development Real-time circuit simulator and editor used to design analog and digital circuits http://praeclarum.org/post/42378027611/icircuit-code-reuse-part-cinq
• #39: Single Solution for iOS, Android, and Windows Leverage Entire Microsoft Ecosystem: ReSharper Team Foundation Server Azure ASP.NET Favorite Code Coverage and Profiling Tools Starter Compatible Visual Studio 2012, 2013, and 2015 including Community Edition
• #40: Xamarin Studio is available for Android development on the PC. Xamarin Studio on Mac offers: Android, iOS and Mac development World Class IDE with great features: Code Analysis Upload to Test Flight Git & Subversion Integration Code Completion Code Navigation Easy transition from Visual Studio The same Solution & Projects open in BOTH Xamarin Studio and Visual Studio!
• #44: If you are looking to get started will a full baked application simply head over to Xamarin’s pre-built page featuring these apps and many more!
• #47: Xamarin Forms is a new set of APIs allowing you to quickly and easily write shared User Interface code that is still rendered natively on each platform, while still providing direct access to the underlying SDKs if you need it.
• #48: We see here the Xamarin approach we talked about earlier This enables you to be highly productive, share code, but build out UI on each platform and access platform APIs With Xamarin.Forms you now have a nice Shared UI Code layer, but still access to platform APIs You can start from native, pick a few screens, or start with forms, and replace with native later
• #49: Xamarin.Forms is much more that just a framework and includes everything you need to get up and running to build out full native applications. If you are used to MVVM type of development you will feel right at home.
• #50: Here is a quick example of a login page: Notice the data binding on the Entries Text fields. Additionally, there is a LoginCommand. Each has a native user interface
• #51: Pick what is right for you! Xamarin has this nifty guide to help you decide to go traditional or with Xamarin.Forms
• #52: First you have a set of pages for each screen of your application There are things like Content, and MasterDetail which gives you a nice flyout With a tabbed view you get the correct look on each platform iOS on bottom, Android on top, and on WP you have a Pivot control Inside of a page are layouts A lot of options from something simple like a stack panel to complex and powerful grids
• #53: You have more than 40 controls, layouts, and pages to mix and match from. These are all of the controls you have out of the box, you can of course create your own. What is unique is you get the native control and have access to it. Consider an Entry Field On iOS it is mapped to UITextField Android it is EditText Windows Phone it is a TextBox
• #54: Xamarin.Forms also has a great ecosystem of controls from vendors you might know!
• #55: With Xamarin.Forms you can easily extend and embed custom views, mix and match screens, called native apis, or even easily migrate to a traditional app and share your backend logic.
• #56: A unique aspect of Xamarin.Forms is an abstraction over the user interface, but what about the platform specific functionality that makes these devices so special? That is where plugins for Xamarin come in.
• #57: What is this stuff that we talk about up here?
• #58: This is the platform specific code no matter how you are developing traditional Xamarin or with Xamarin.Forms. However, many platform APIs are the same bit of functionality, but with different APIs. What if we had 1 API?
• #59: For instance text to speech, what if we could just say “Speak” and it would speak text with the underlying API.
• #60: This is what Plugins for Xamarin are for! 1 API for all common APIs: Camera GPS Settings Notifications Battery And so much more!
• #62: Well there are several challenges that we must overcome as mobile developers including….
• #63: First let’s take a look at the shear number of configurations there are between iOS and Android. As iOS progresses this number is only set to increase, and on Android it is already a HUGE number of configurations to even think about testing. iOS: 7, 7.1, 8, 8.1, 8.2
• #64: OpenSignal is a global app that publishes an annual report on Android device fragmentation based on the distinct Android device types that download their app. This is their August 2014 data, with an astonishing 19,000 device types using their app, up by 60% from just last year. Different device operating systems, form factors, screen sizes, resolutions, chip sets, and manufacturer modifications make it difficult to know that your app will work well on all devices
• #65: Looking at just a few of the screen sizes of Samsung devices you couldn’t even fit all of them on the screen, so how do you handle this problem?
• #66: The fragmentation isn’t just in the devices, but as we start to build on our applications you soon found out they are ever increasingly complex.
• #67: With a simple command you can simulate all of your users interactions to build out a great test suite that can be run over and over again.
• #68: This is where Xamarin.UITest comes in to help with this shift. Xamarin.UITest is a framework that ties in directly to the Nunit testing framework to write the UI tests. You can even run them directly against a simulator for free to do regression tests on your applications. Freely available for testing on a Simulator*
• #69: Take test scripts and test again thousands of physical devices! All Xamarin subscribers get free device time! Check store.xamarin.com for details.
• #71: Xamarin Insights is a new product from Xamarin, currently in preview for all of your apps to handle crash reporting and analytics.
• #72: Xamarin.Insights, currently in preview, enables us to support all of our apps from a full cross platform API.
• #76: Xamarin.Insights, currently in preview, enables us to support all of our apps from a full cross platform API.
• #78: Get started today with free 30 day trial of Xamarin at xamarin.com