Cross platform app development with xamarin.forms
•Download as PPTX, PDF•
0 likes•141 views
Microsoft MVP, Shahriar Hossain shows you how to build your first cross platform app with Xamarin. With Xamarin.Forms, you're able to get maximum code reuse to quickly build fully native apps for Android, iOS, and Windows. In this session learn how to share C# code to define the UI and business logic, enabling you to design your screens, fix bugs, and write your app just once. With Xamarin for Visual Studio, you use the language and IDE you know and love to get to market fast, sharing one codebase across all platforms.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Cross platform app development with xamarin.forms
Similar to Cross platform app development with xamarin.forms (20)
More from Shahriar Hossain
More from Shahriar Hossain (14)
Recently uploaded
Recently uploaded (20)
Cross platform app development with xamarin.forms
- 1. Cross Platform app development with Xamarin Shahriar Hossain Microsoft MVP @shossain_tweet #Career Guideline
- 2. Silo Approach Build Apps Multiple Times • Multiple Teams • Multiple Code Bases • Different toolsets
- 3. HTML - Write Once, Run Anywhere Approach • Lowest common denominator • Browser fragmentation • Developing & designing for 1 platform, happen to get other platforms
- 4. Start with HTML5/CSS3/JavaScript Use PhoneGap Deploy to platforms
- 9. Xamarin’s Unique Approach • Native User Interface • Native Performance • Shared code across platforms • C# & .NET Framework • Full API Coverage
- 10. With Xamarin.Forms: more code-sharing, native controls Traditional Xamarin approach Shared UI Code Xamarin.Forms Unique Approach
- 15. Content MasterDetail Navigation Tabbed Carousel Pages
- 16. Stack Absolute Relative Grid ContentVie w ScrollView Frame Layouts
- 17. 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
- 18. Use a single API to generate native, platform-specific user interfaces At runtime, each Xamarin.Forms page and its controls are mapped to platform-specific native user interface elements Xamarin.Forms Example
- 20. .NET + Windows APIs
- 21. .NET + iOS APIs | 100% Coverage
- 22. .NET Android APIs | 100% Coverage
- 24. Xamarin.iOS does full Ahead Of Time (AOT) compilation to produce an ARM binary for Apple’s App Store. Native Performance Xamarin.Android takes advantage of Just In Time (JIT) compilation on the Android device.
- 26. Technology Stack
- 30. Anything you can do in Objective-C, Swift, or Java can be done in C# with Xamarin using Visual Studio
- 31. Real-time monitoring. Track crashes and exceptions to understand what is happening with live users.
- 32. DEMO
- 35. Thank You
Editor's Notes
- Multiple Teams Multiple Code Bases Expensive & Slow Positive = Great apps delivered to user’s platform Negative = Development hampered by multiple code bases & fragmentation
- Unhappy Users Unhappy Developers Increase in Abandoned Apps Limited to what is implemented PhoneGap, Cordova, Telerik Platform Silver (swift)
- Native With Code Sharing ...... 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
- 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
- http://blog.xamarin.com/cheat-sheet-for-top-mobile-app-controls/
- 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
- Inside of a page are layouts A lot of options from something simple like a stack panel to complex and powerful grids
- 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
- 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.
- 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.
- 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#.
- The same is true for Android as well.
- There is no compromise on performance. Xamarin apps look and feel native because they are native.