4 steps to great xplat apps (M
•Download as PPTX, PDF•
0 likes•391 views
The document outlines 4 steps to create great cross-platform apps using MvvmCross: 1. Use the MVVM pattern with MvvmCross for cross-platform code reuse 2. Maximize shared code by using a PCL and consistent app structure 3. Declaratively bind views to view models for separation of concerns 4. Leverage platform-specific features through plugins while keeping most code shared
Recommended
More Related Content
What's hot
What's hot (19)
Similar to 4 steps to great xplat apps (M
Similar to 4 steps to great xplat apps (M (20)
Recently uploaded
Recently uploaded (20)
4 steps to great xplat apps (M
- 1. 4 steps to great x-plat apps Alexey Strakh Alex Sorokoletov
- 2. Hey, we’re Alexey and Alex • Certified Xamarin Developers • Microsoft MVP • Multiple apps with Xamarin and MvvmCross • Recent example - one solution with iOS/Android/WindowsPhone/WPF Alexey Strakh @AlexeyStrakh Alex Sorokoletov @AlexSorokoletov
- 3. Step 1. Use MVVM
- 4. MvvmCross is the way 1.Crossplatform 2.Lots of components baked in 3.Proven solution 4.Extendable and opensource 5.Crossplatform glue between view and viewmodels
- 5. Step 2. Reuse the code 1. PCL 2.Solution structure 3.App structure
- 6. Use PCL • Lots of 3rd party components (nuget) • Flexibility • One place • Less efforts to maintain code
- 7. Proven solution structure • App.Core project (Shared code) • App.Android project (sometimes App.Droid) • App.iOS project • App.OtherPlatform projects
- 8. Mvx app structure • Components • Startup • Navigation • Presentation layer
- 9. App.cs code
- 10. MvxSetup.cs
- 11. AppDelegate.cs
- 12. Maximize shared code Top reused things in crossplatform applications: • Icon • Splash • Title • Description Wait!… What about code?
- 13. Demo 1 Hello, x-platform world
- 14. Step 3. Databind your UI Views and ViewModels
- 16. Demo 2 Bindings
- 17. Step 4. Use platform features • Facebook native authentication • Photos and camera access • Push notifications • Mail composer • Background execution
- 19. MvvmCross plugins • Location • Phone dial • Picture chooser • Compose email • Vibrate • Sqlite • Social authentication • Many other at drmtm.us/mvxplugins
- 20. Demo 3 Real API integration
- 21. Advanced topics • View presenters • Custom views • Custom bindings • Mvx app lifecycle
Editor's Notes
- First 90 seconds of pitch people decide are they listening actively, or just zoning out We're developing for Xamarin for 2 recent years Lots of published apps Xamarin Certified folks Specify how we handle questions: “If you have any questions, I'll be happy to answer them as we go along."
- Mvvm pattern overview: ViewModel keeps business logic
- Glue because of databinding
- Story about taxi app (android, iOS) and street selections: We're using 3rd party service. This service has own set of streets there (yes!). We have objective C taxi app, it uses apple maps, and android app - uses google maps. We have to add new streets in two places - objc/android. Crazy stuff
- Mvx app startup : App, IMvxAppStart, Setup (show main events in code) All navigation should be kept in core, this is key! (ViewModels, ViewModel life-cycle, ShowViewModel) MvxViews is extension of native view s which you can override and they are already integrated with Core
- Ask what is usually shared in code between cross platforms apps? Data Model? Service API commucation? What about View logic (that is when we place it in viewmodels and reuse with bindings) What about database access (sqlite) What about other stuff (platform specific)
- Sample solution, hello xworld 4square/SimpleLatitude API search example: 1st view has textbox to enter criteria, 2nd view shows results.
- What is databinding in general, how it helps and why we should do this
- Bind textbox to property Button to command List to results
- Implement API interface Integrate it into the core Bind results to the UI