xamarin forms

19
Xamarin Forms Ordertracker Peter Major Dec 11, 2014

Upload: peter-major

Post on 22-Feb-2017

320 views

Category:

Software


0 download

TRANSCRIPT

Page 1: Xamarin Forms

Xamarin FormsOrdertracker

Peter MajorDec 11, 2014

Page 2: Xamarin Forms

.NETWPFAngularJSXamarin - SeptXamarin Forms - Nov

Background

Page 3: Xamarin Forms

Customers:Where is my order?

Restaurants:Where are my drivers?

In pilot at 11 restaurants - iOS only

Ordertracker | Driver App

Page 4: Xamarin Forms

UX

Page 5: Xamarin Forms

Demo

Page 6: Xamarin Forms

- Xamarin code reuse

- Two UI layouts

- New developers learn two technologies

Without Forms

Page 7: Xamarin Forms

- One page for iOS and Android

- Native look and feel

With Forms

Page 8: Xamarin Forms

Forms

Entry

EntryRenderer EntryRenderer

UITextField EditText

iOS Android

Page 9: Xamarin Forms

Same vs Different

Page 10: Xamarin Forms

- XAML or code

- WPF? Forms will be familiar.

- By feature, not by platform

With Forms

Page 11: Xamarin Forms

- Pages

- Layouts

- Viewshttp://developer.xamarin.com/guides/cross-platform/xamarin-forms/controls/

Xamarin Forms

Page 12: Xamarin Forms

- Subclass the XF “view”Button demo

- Custom rendererEntry demo

Customization

Page 13: Xamarin Forms

- Must write native UIs

- MvvmCross with XF? Probably no.duplication

bindingnavigation

https://github.com/XLabs/Xamarin-Forms-Labs

MvvmCross

Page 14: Xamarin Forms

- Used internally by XF

- Static singleton

- Strange generic syntax

MessagingCenter

Page 15: Xamarin Forms

- Service Locator pattern

- Static singleton (again)

- No constructor injection

DependencyService

Page 16: Xamarin Forms

- App-wide resource dictionaries- Behaviors- Triggers- Dynamic resources- Styles

1.3 Preview

Page 17: Xamarin Forms

- New or Existing product?

- New or Existing team?

Should I use XF?

Page 18: Xamarin Forms

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

Good

Page 19: Xamarin Forms

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

Bad