Xamarin Forms allows developers to write cross-platform mobile apps for iOS and Android using shared C# code. It provides common UI elements like buttons and entries that are rendered natively on each device. While Forms handles much of the cross-platform code sharing, custom renderers may still be needed for platform-specific customization. The framework uses MVVM and messaging patterns to support data binding and communication between components. Xamarin Forms is best for new teams or products where a single shared UI is desired and the initial customization requirements are not extensive.

1. Xamarin Forms
OrdertrackerPeter Major
Dec 11, 2014

2. .NET
WPF
AngularJS
Xamarin - Sept
Xamarin Forms - Nov
Background

3. Customers:
Where is my order?
Restaurants:
Where are my drivers?
In pilot at 11 restaurants - iOS only
Ordertracker | Driver App

4. UX

5. Demo

6. - Xamarin code reuse
- Two UI layouts
- New developers learn two technologies
Without Forms

7. - One page for iOS and Android
- Native look and feel
With Forms

8. Forms
Entry
EntryRenderer EntryRenderer
UITextField EditText
iOS Android

9. Same vs Different

10. - XAML or code
- WPF? Forms will be familiar.
- By feature, not by platform
With Forms

11. - Pages
- Layouts
- Views
http://developer.xamarin.com/guides/cross-platform/xamarin-forms/controls/
Xamarin Forms

12. - Subclass the XF “view”
Button demo
- Custom renderer
Entry demo
Customization

13. - Must write native UIs
- MvvmCross with XF? Probably no.
duplication
binding
navigation
https://github.com/XLabs/Xamarin-Forms-Labs
MvvmCross

14. - Used internally by XF
- Static singleton
- Strange generic syntax
MessagingCenter

15. - Service Locator pattern
- Static singleton (again)
- No constructor injection
DependencyService

16. - App-wide resource dictionaries
- Behaviors
- Triggers
- Dynamic resources
- Styles
1.3 Preview

17. - New or Existing product?
- New or Existing team?
Should I use XF?

18. - One UI layout
- Very customizable
- Initial customization
- Develop by feature
- Very active development
Good

19. - Renderers have “internal” code
- Bugs, fix with renderers
- No app-wide shared resources (in stable)
- No XAML designer
Bad