Use Shared Project for Desktop WPF, 8.1 Universal, and 10 Universal?

[Don Geronimo]

I'm in the process of making a specification and mockups to present to two US-MN food pantries for an application to help ease their data collection and to provide the required reports they need to provide to fulfill federal and state TEFAP requirements. Like a good boy my current specification is using interfaces and MVVM so that I (or others) can work on the components in parallel. However, I'm faced with a curious situation, in that food pantries (and non-profits in general) have to work with what technologies they have on hand.

With that understanding, assuming I continue being good and use MVVM to keep the business logic away from the view, is a Visual Studio solution like this possible:

• Shared (All ViewModels and business-logic interfaces, with compiler directives wherever an API is not universal as needed; use Xamarin?)
• Windows Desktop WPF (UI/UX with no business logic; references Shared)
• Windows 8.1 Project (UI/UX with no business logic; references Shared)
• Windows Phone 8.1 (UI/UX with no business logic; references Shared)
• Windows 10 UAP (UI/UX with no business logic; references Shared)
• iOS (UI/UX with no business logic; Will need Xamarin compiler directives in Shared; references Shared; not in current timeline; future-proofing)
• Android (UI/UX with no business logic; Will need Xamarin compiler directives in Shared; references Shared; not in current timeline; future-proofing)
• Mac (Future-Proofing; use Xamarin.Mac)
• Linux (Future-Proofing; use Xamarin.GTK#)
• Web (Quite honestly, when it comes to what hardware this will be used in, it might be easier to just create a web app using PHP or ASP.Net)

Is this kind of project possible? My main focus right now is probably just Windows Desktop using WPF and Windows 8.1, with the other platforms coming at a later time. But is this actually possible and/or realistic?

 

[MikeInBA]

dear lord man lol. I took one look at that list and got a headache. If I was in that situation I would go with a web based product for everyone. Downside is your going to have crap time with browser compatibility.