Xamarin for ASP.NET developers
Context:
For many Xamarin might be just a next episode in .NET journey.
Before I started Xamarin I did: ADO.NET, WinForms, WPF and Windows Phone……
It happens that your current project is Enterprise Solution and now time have come, that it need some mobile client app.
Team is full stack .Net developers with rage of skills except mobile but will to do mobile apps.
What happen to me was exact this case so doable, check out what you need to know.
This is work in progress so I will update when Have time.
You probably don’t have time to read, and I have no time to write.
I will try to be minimalistic.
Assumptions
Before you start I hope you visited:
and know what is Xamarin.Native and Xamarin.Forms.
Xamarin.Native is kind of hard and sometimes alien that is why I won’t recommend it to start with. If want to have fast effect and you are new in Xamarin, for now doing something else than Forms would NOT be an option.
Later by shortcut Xamarin I will understand Xamarin.Forms project.
Why Xamarin.Forms?
Tools:
Real time UI building
Warm up:
- Xamarin.Forms: Turn on Hot Reload
- Xamarin.Forms: Hot Reload 1: Tests
- Design time data Hot Reload+MVVM
- Hot Swap View Models: Creative Mess
- Hot Swap View Models: More creative mess
More advance topics:
Consuming Api
Styles
- Pixel Perfect and validating UI
- LEGO UI framework
- CSS/LESS
- Pseudo HTML
- text
- buttons
- navigation bar
- native UI/ The Date picker
- Hack it with Canvas!
- internalization
Architecture
- This is mobile don’t over engineer!!!
- mvvm (smaller MVC)
- thinking cross-platform
- error handling / MVA
- native/device services
Routing
- Routing and navigation service
- refreshing depended views
The Native APIs
Real World Production App Case Study Presentation