This is a long shot, but I was thinking that someone else must be considering of how to solve this;
The Xamarin ASPNZ app is a nice start and handles much of the Async traffic and authentication. I am embarking on replicating the main dashboard of my app space in the Xamarin app . There is no sense in replicating controls and using API's to bind them as the ASP core app is very responsive. Except for the grids, they seem to render well on most mobile device (the grids do have some issues on droid phones) I can’t see a reason to replicate this with native or XF controls.
So, my approach is to allow the main dashboard to render inside a WebView control implemented inside the APSNZ Xamarin client appl. Several issues arise from this scheme;
- Stripping off duplicate headers (allow ASNZ client app to manage navigation)
- duplicate footers
- Push notifications
- managing screen call stack to ensure app does not go outside dashboard frames.
- Custom navigation ( I have an API scheme for this )
Anybody already thinking along these lines or see more issues with this that I just mentioned? Any input is welcome on this moving the Xam Client further along. Thanks!
1 Answer(s)
-
0
my little advice could be, stripping off the dashboard to a partial view. then use it in the original place as now. and for the mobile create a new page without current layout (no header-footer etc.) and use the same partial view there. so that you can share the dashboard with the current layout and for the new mobile layout.
