2 ms·
But why _force_ it with different APIs? Is it impossible to imagine a set of applications (ie: generic Bank of America banking app: take pictures of checks and
by dragontamer 11y ago
But why _force_ it with different APIs?
Is it impossible to imagine a set of applications (ie: generic Bank of America banking app: take pictures of checks and send them in sorta thing) where the UWP model doesn't help?
If you need a 2nd application for your task, then write two different UWP applications. If you don't, then write one application with two XAMLs. If you want a very cheap program, write one application with a "responsive" XAML that works on all systems.
By unifying the code base, you have the flexibility to do whatever code you need. Different code paths if the applications are grossly different, or the same code path if you need to save some money.