Is MasterDetail page slow in Xamarin Forms? Increases startup time?

batmacibatmaci DEMember ✭✭✭✭

I only used so far freshmvvm and recently found out that freshmvvm masterdetail implementation increases my startup time more than 4secs if I have several navigation pages on it. Basically; It executes viewmodel constructors and page InitializeComponent(); which means it pre-caches pages for every navigation page defined on masterdetail page. There is no way to prevent this. I tried to use global parameter to lazy load these pages but It doesnt re-request constructors if I select from masterdetail. So my question is; is it freshmvvm's bad implementation or it is a general issue for xamarin forms? what is the suggested master detail page implementation without effecting startup time? Can I even load it not in app.cs constructor but after navigation page appears? like doing it in onstart function


Sign In or Register to comment.