"Intro to-xamarin.forms", Кирилл Стативкин, Microsoft Student Partner
•Download as PPTX, PDF•
1 like•267 views
This document introduces Xamarin.Forms, which allows developers to write native mobile apps using C# that share code across platforms. Xamarin.Forms apps have native performance and access platform APIs while using shared UI code, layouts, and controls defined in C# and XAML. This allows building iOS, Android, and Windows apps with one shared codebase instead of maintaining separate codebases. The document demonstrates building an app with a tabbed page layout and shared login page in XAML, and discusses Xamarin.Forms' included layouts, controls, and platform API coverage on iOS, Android and Windows.
Report
Share
"Intro to-xamarin.forms", Кирилл Стативкин, Microsoft Student Partner
- 1. Intro to Xamarin.Forms Kirill Stativkin Microsoft Student Partner kirill.stativkin@studentpartner.com
- 2. Microsoft Student Partner Ukraine/France C# Mobile developer Full Stack C# developer Iafoo.com France https://www.facebook.com/kirill.stativkin Xamarin User Group Ukraine https://www.facebook.com/groups/xamarin.ua/
- 3. Make it fast, easy, and fun to create great native mobile apps. Xamarin’s Mission
- 4. What is native? • Xamarin apps look and feel native because they are native Native User Interfaces Native API Access Native Performance
- 5. The Silo Approach Build App Multiple Times
- 6. The Write-Once-Run-Anywhere Approach Lowest Common Denominator
- 7. Xamarin’s UniqueApproach Shared C# codebase • 100% nativeAPI access • High performance iOS C# UI Android C#UI Windows C#UI Shared C# Mobile
- 9. Native Performance Xamarin.iOS does full Ahead Of Time (﴾AOT)﴿ compilation to produce an ARM binary for Apple’s App Store. Xamarin.Android takes advantage of Just In Time (﴾JIT)﴿compilation on the Android device. .NET C# Compile and Link .APK Bindings IL + JIT Runs Natively
- 12. Xamarin +Xamarin.Forms Traditional Xamarin Approach With Xamarin.Forms: More code-‐sharing, all native Shared UI Code Shared C# Backend iOS C# UI Android C# UI Windows C# UI Shared C# Backend
- 13. What’sincluded ✓ 40+ Pages, layouts, and controls (﴾Build from code behind orXAML)﴿ ✓ Two-‐waydata binding ✓ Navigation ✓ Animation API ✓ Dependency Service ✓ Messaging Center Shared UI Code Shared C# Backend
- 14. Layouts Pages Stack Absolute Relative Grid ContentView ScrollView Frame Content MasterDetail Navigation Tabbed
- 15. ActivityIndicator BoxView Button DatePicker Editor Entry Image Label ListView Map OpenGLView Picker ProgressBar SearchBar Slider Stepper TableView TimePicker WebView EntryCell ImageCell SwitchCell TextCell ViewCell Controls
- 16. Windows Xamarin.Forms StackPanel StackLayout TextBox Entry ListBox ListView CheckBox Switch ProgressBar ActivityIndicator Grid Grid Label Label Button Button Image Image Date/TimePicker Date/TimePicker Control Comparison
- 17. <?xml version="1.0" encoding="UTF-‐8"?> <TabbedPage xmlns="http://xamarin.com/schemas/2014/forms" xmlns:x="http://schemas.microsoft.com/winfx/2009/xaml" x:Class="MyApp.MainPage"> <TabbedPage.Children> <ContentPage Title="Profile" Icon="Profile.png"> <StackLayout Spacing="20" Padding="20" VerticalOptions="Center"> <Entry Placeholder="Username" Text="{Binding Username}"/> <Entry Placeholder="Password" Text="{Binding Password}" IsPassword="true"/> <Button Text="Login" TextColor="White" BackgroundColor="#77D065" Command="{Binding LoginCommand}"/> </StackLayout> </ContentPage> <ContentPage Title="Settings" Icon="Settings.png"> <!-‐-‐ Settings -‐-‐> </ContentPage> </TabbedPage.Children> Native UI from sharedcode
- 18. Demo
- 22. Demo
- 24. Data pages
- 26. Demo
- 28. Kirill Stativkin Microsoft Student Partner Kirill.Stativkin@studentpartner.com Thank you. Questions? https://www.facebook.com/groups/xamarin.ua/
Editor's Notes
- Fix this with website stuff
- Expensive to staff multiple platform-specific teams Expensive to maintain multiple code bases Slows innovation
- Poor user experience – API coverage – Performance High abandonment rates Wasted investment