Introduction to xamarin

Notas del editor

• #11: Let’s talk about the state of mobile development today
• #12: Multiple Teams Multiple Code Bases Expensive & Slow Positive = Great apps delivered to user’s platform Negative = Development hampered by multiple code bases & fragmentation
• #13: Unhappy Users Unhappy Developers Increase in Abandoned Apps Limited to what is implemented
• #14: UI build natively per platform, leveraging C# C# + XAML C# + XML C# + XIB One shared app logic code base, iOS, Android, Mac, Windows Phone, Windows Store, Windows
• #15: 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
• #16: Let’s talk a bit about why you would choose Xamarin as your development platform.
• #19: Major announcement at the end of 2013: Truly Portable Class Libraries Support for VS 2013 Special offers for MSDN Subscribers 20 City Roadshow!
• #21: Statically typed so you avoid a pitfall of errors that afflict other languages. Use LINQ in your Xamarin projects to query, filter and select data from in-memory arrays, or from databases such as SQLite. Parsing XML is easy Setting up event handling is a breeze Intellisense, lambdas, etc. are all awesome.
• #22: 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.
• #23: 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
• #24: 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
• #25: 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!
• #26: Use your favorite libraries like Json.NET!
• #28: There is no compromise on performance. Xamarin apps look and feel native because they are native.
• #29: 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
• #31: Compiles down to APK or IPA that you can distribute anywhere, any store. Or even internal enterprise
• #32: 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
• #34: Let’s talk a bit about C# and why it is awesome.
• #39: 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.
• #40: 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#.
• #41: The same is true for Android as well.
• #43: Portable Class Libraries are awesome! You can write all of your C# code in one assembly and share across all platforms Before the Xamarin & Microsoft Partnership PCLs were limited ONLY to Windows Platforms Now add official support to create and use PCLs in Visual Studio and Xamarin Sudio
• #45: Xamarin Studio PC -> Android Mac -> iOS, Android, Mac Visual Studio: iOS, Android Windows
• #46: Additionally Supports Visual Studio 2010, 2012, & of course 2013 Additionally support desktop apps on Windows: WPF, ASP.NET, Silverlight, WinForms! The same Solution & Projects open in BOTH Xamarin Studio and Visual Studio!
• #47: Connect to Mac build host for iOS development Show list of all iOS devices and Simulators to debug on Shows all Android devices and emulators X86, Arm, Genymotion.. Take advantage of all debugging power of VS
• #48: 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!
• #49: State of the art features: View different Themes View different device sizes Multi-view editing!
• #51: Add high quality pre-built app components directly from Visual Studio. Includes dozens of beautiful UI controls and web services – adding a theme or a 3rd party library is just a few clicks away Complements existing .NET NuGet ecosystem Differentiator: focus on UI controls and themes – we are making developers better designers across all platforms
• #52: Generates a full report of all method calls to determine compatibility with Xamarin.Android, Xamarin.iOS, Windows Phone, and Windows 8.
• #53: Demo time if so desired
• #54: 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
• #55: 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.
• #56: 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
• #57: Inside of a page are layouts A lot of options from something simple like a stack panel to complex and powerful grids
• #58: 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 Phoneit is a TextBox
• #59: Here is an example of Xamarin.Forms in action using C# in the code behind to create a login screen. You can see how each is rendered with the native controls on iOS, Android, and Windows Phone.
• #60: Xamarin.Forms is extremely extensible as well allowing you to customize controls or add your own. You can always get down and call platform specific APIs, so you aren’t limited in any way.
• #63: Demo time if so desired
• #64: Demo time if so desired
• #65: Demo time if so desired
• #66: If you look at the wide range of devices there is no way to tackle everything. These are low numbers for just the top manufactures on Android.
• #67: Test Cloud enables you to write Automated Test in C# to run against hundreds of physical devices. This means you get real results from real devices to you know how your app will look, feel, and act on a wide range of devices before your users run into issues.
• #68: Demo time if so desired
• #72: Demo time if so desired