Downloaded 43 times
Uploaded byMichael Ridland
Introduction to Xamarin.Forms and Lessons Learnt
The document provides an introduction to Xamarin.Forms, covering features such as code-sharing, layout, controls, data binding, and navigation, with practical demos including a stocks app. It discusses extensibility options like custom renderers and using a dependency service to access platform-specific SDK features. Additionally, the document shares insights, tips for effective use, and resources for further learning related to Xamarin.Forms development.
Introduction to Xamarin.Forms and Lessons Learnt
- 1. Introduction to Xamarin.Forms www.michaelridland.com @rid00z
- 2.
- 3. Xamarin + Xamarin.Forms With Xamarin.Forms: more code-sharing, native controls Traditional Xamarin approach Shared UI Code www.michaelridland.com @rid00z
- 4. What’s Included 40+ Pages, Layouts, and Controls Build from code behind or XAML Two-way Data Binding Navigation Animation API Dependency Service Messaging Center Shared UI Code www.michaelridland.com @rid00z
- 5. Pages Content MasterDetailNavigation Tabbed Carousel www.michaelridland.com @rid00z
- 6. Layouts Stack AbsoluteRelative Grid ContentView ScrollView Frame www.michaelridland.com @rid00z
- 7. Controls ActivityIndicator BoxViewButton DatePicker Editor Entry Image Label ListView Map OpenGLView Picker ProgressBar SearchBar Slider Stepper TableView TimePicker WebView EntryCell ImageCell SwitchCell TextCell ViewCell www.michaelridland.com @rid00z
- 8. DEMO 1 DisplayingList of Data www.michaelridland.com @rid00z
- 9. Model-View-ViewModel Data Data View ViewModel Model How to display information What to display Flow of interaction Business Logic Data objects Events www.michaelridland.com @rid00z
- 10. Model-View-ViewModel Data ViewViewModel Model Events Xamarin.Forms Data Binding www.michaelridland.com @rid00z
- 11.
- 12.
- 13.
- 14.
- 15. DEMO 2 StocksApp www.michaelridland.com @rid00z
- 16.
- 17. Extensibility Custom Renderer Easily subclass any control you wish to customize. Add your own custom controls. Add custom bindable properties http://developer.xamarin.com/guides/cross-platform/ xamarin-forms/custom-renderer/ www.michaelridland.com @rid00z
- 18. Extensibility Standard EntryControl www.michaelridland.com @rid00z
- 19. Extensibility Step 1:Custom Xamarin.Forms Control www.michaelridland.com @rid00z
- 20. Extensibility Step 2:Use Custom Control in our shared Pages www.michaelridland.com @rid00z
- 21. Extensibility Step 3:Implement Custom Renderer www.michaelridland.com @rid00z
- 22. Extensibility Step 4:Export Renderer www.michaelridland.com @rid00z
- 23. Extensibility Dependency Service Lets shared code access platform-specific SDK features via an Interface implementation www.michaelridland.com @rid00z
- 24. Extensibility Step 1:Interface www.michaelridland.com @rid00z
- 25. Extensibility Step 2:Implement on each Platform www.michaelridland.com @rid00z
- 26. Extensibility Step 3:Register with Dependency Service www.michaelridland.com @rid00z
- 27. Extensibility Step 4:Access from shared code www.michaelridland.com @rid00z
- 28. DEMO 3 StocksApp + Text to Speech www.michaelridland.com @rid00z
- 29.
- 30.
- 31. Navigation Root Page: NavigationPage – Gives each page an INavigation Standard Navigation Navigation.PushAsync(page: nextPage); Navigation.PopAsync(); Modal Navigation Navigation.PushModalAsync(page: modalPage); Navigation.PopModalAsync(); www.michaelridland.com @rid00z
- 32. Messaging Center MessagingCenter.Subscribe<T>(objectsubscriber, string message, Action<T> callback); MessagingCenter.Send(T item, string message); www.michaelridland.com @rid00z
- 33. Messaging Center MasterPage: Detail Page: www.michaelridland.com @rid00z
- 34. Xamarin.Forms My Experiencesand Tips www.michaelridland.com @rid00z
- 35. Good Parts Fastand Easy to Create Cross Platform UI Elements Some good features/extensibility points - custom renderers, message centre etc. The idea and concept is great. But we all need to pitch in to make it better, aka Xamarin.Forms.Labs. www.michaelridland.com @rid00z
- 36. Not so goodparts At the moment it still stuffers from common denominator. e.g. Save and Cancel are different on Android, iOS and WP. The coverage of UI elements isn’t huge Tiny Cuts - No Bordering, ToolBarButtons only on rightside, Only TapGestureRegonizers, Picker not databound www.michaelridland.com @rid00z
- 37. Tip 1. Don’tfight the framework ‘I want Cancel here because that’s how I do it in iOS’… ‘I want swipe cell because that’s how I do it in iOS’… If you use Xamarin.Forms, try not to bring in pre conceptions of how you want your UI to be. You can build nice UI’s with Xamarin.Forms but you just need to be within it’s constraints and no swipe cells. www.michaelridland.com @rid00z
- 38. Tip 2. Prototype Prototype your app in Xamarin.Forms.. see if it’s going to work… Traditional Xamarin.iOS and Xamarin.Android is still great if you want a amazing experience on all platforms. www.michaelridland.com @rid00z
- 39. Tip 3. Xamarin.Forms.Device.StartTimer www.michaelridland.com @rid00z
- 40. Tip 4. StackLayout,BoxView to style forms www.michaelridland.com @rid00z
- 41. Tip 5.Preview PETZOLD’sXamarin.Forms Book http://blogs.msdn.com/b/microsoft_press/archive/2014/10/06/www.michaelridland.com @rid00z
- 42. Tip 6. Xamarin.Forms.Labs Fill some gaps in Xamarin.Forms… Labs Demo! (*Labs is really labs code, recommended to work off the code) www.michaelridland.com @rid00z
- 43. Tip 6. Xamarin.Forms.Labs What else is there? - HybridWebView can be useful when used Razor! - INetwork service get the InternetConnectionStatus (WIIFI)? - Photo library/take a photo - Extended TextFields - Fonts and Border properties - + More www.michaelridland.com @rid00z
- 44. Tip 7. Givingback to Xamarin.Forms.Labs We need you! - Fork Xamarin.Forms.Labs in GitHub - Clone to your local machine - Build the Xamarin.Forms.Labs Project - Add the projects into your project - add new features - Do a pull Request back into the Project www.michaelridland.com @rid00z
- 45. Tip 8. BindableProperty code template public static readonly BindableProperty $Name$Property = BindableProperty.Create<$owner$, $type$>(p => p.$Name$, default($type$)); public $type$ $Name$ { get { return ($type$)GetValue($Name$Property); } set { SetValue($Name$Property, value); } } www.michaelridland.com @rid00z
- 46. Tip 9. XamarinHack Day Sydney Xamarin Hack Day Sat 6th Dec www.xamarinhackday.com Please come along for a great day! * Want to present? Twitter me @rid00z www.michaelridland.com @rid00z
- 47. Tip 10. LayerViews using AbsoluteLayout www.michaelridland.com @rid00z
- 48. Resources Documentation http://developer.xamarin.com/guides/cross-platform/xamarin-forms/ XAML Documentation http://developer.xamarin.com/guides/cross-platform/xamarin-forms/xaml-for- xamarin-forms/ Samples https://github.com/xamarin/xamarin-forms-samples www.michaelridland.com @rid00z
- 49. Q & A Find Me: rid00z@gmail.com www.michaelridland.com @rid00z
Editor's Notes
- #3 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.
- #4 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
- #6 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
- #7 Inside of a page are layouts A lot of options from something simple like a stack panel to complex and powerful grids
- #8 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
- #9 Let’s take a look at getting started with Xamarin.Forms and displaying some data across all platforms.
- #10 Xamarin.Forms was build with MVVM in mind. It is optional, but if you are used to an MVVM style of programming you are going to feel right at home. MVVM is an architectural pattern that is used to abstract our Views/Pages from our Business Logic Let’s look how it works. Our View just knows how to display Information It can pass data and event back and forth to the ViewModel The ViewModel simply tells the View what to display and can accept events. The model sits off to the side and only our ViewModel interact with it to gather data (maybe from the database or REST services)
- #11 The “Magic” of MVVM is with a Data Binding framework. This allows us to change data in the ViewModel and our View automatically reacts. This is build into WPF/Windows Phone/Windows Store, but does not exist for Android or iOS. However, Xamarin.Forms has a full data binding framework built right in. Let’s take a look.
- #12 The core of data binding comes with “INotifyPropertyChanged” This allows any UI element to subscribe and “Bind” to a property and react when the “PropertyChanged” method is raised.
- #13 When we update a field such as FirstName we trigger a property changed and anyone subscribed gets notified.
- #14 Here we are creating a label and the “TextProperty” is being bound to the “FirstName” property in the ViewModel.
- #15 We can also setup 2 way data binding so if our view update so does our ViewModel and vise versa.
- #16 Let’s take a look at some data binding in action, which we will access through XAML!
- #18 The extensibility framework in Xamarin.Forms enables us to 1.) Customize any of the built in controls 2.) Use any custom control that we might have developed
- #19 This is a standard Entry control in Xamarin.Forms. As we can see it renders a native iOS TextField for text entry. Let’s say we want to change the look and feel of the control past what is exposed. Well we can create our own version called “MyEntry”
- #20 First we will create our own Xamarin.Forms control in our shared code. In this case we are simply inheriting from “Entry”, however you can even inherit from View which can be anything. Optional: Add custom properties and bindings
- #21 We can simply reference and use this new custom control like any of the other control that come out of the box.
- #22 As I mentioned earlier each Xamarin.Forms control has a custom renderer that knows how to “render” and display the native control. Each Xamarin.Forms control has a Renderer that we can inherit from (including “View” for our custom controls that we might have purchased or created). Here we will inherit from EntryRenderer and customize the actual UITextField control and set the border style and background color.
- #23 The last thing to do is add an export assembly attribute and we are done!
- #25 First step for using the the Dependency service is to setup an Interface that is accessible from your shared code.
- #26 For each platform we plan to support (iOS, Android, and Windows Phone), we will implement the native functionality. For instance here, we are using AVSpeechSynthesizer on iOS to perform TextToSpeech
- #27 The built in dependency service uses an assembly attribute to know what class to use for the interface implementation.
- #28 The dependency service allows you to easily resolve your interface for the platform specific implementation. Here we are playing back “Hello from Xamarin Forms” when we click a button.
- #31 Xamarin.Forms has a complete cross platform animations api as well. It takes advantage of the underlying APIs on each platform such as CoreAnimation on iOS. Additionally, it is completely asynchronous with an async/await api.