08-02-2016, 03:18 AM
Yes, the database will be the same. By choosing to develop the Windows 10 as a Universal Windows Platform application, it will work on any Windows 10 device (phone, pc, tablet, etc). I will also be able to distribute it through the Windows Store. If I had chosen to write MobileSheetsPro with a cross-platform library, I would not have been able to sell it on the Windows Store, and it probably would not work on phones. It certainly would not have looked like a Windows 10 app either. I also would not have been able to handle touch gestures and such, as that is built in to Microsoft's new API.
It will be your choice if you want to use the Window 10 version to manage your library, but it is not set up like the companion application. It is not designed to manage the library of an external device - it is going to be identical to the Android version in terms of functionality and behavior. If you mirror your library between your PC and your tablet, then you could use the Windows 10 version for this purpose. Once I add more synchronization features, this may become a feasible option for replacing the companion app.
If a huge demand for a Linux version develops at any point, I will certainly consider porting over the code to something like C++/wxWidgets, but I will have to figure out how to sell/license that version, as I'm currently relying on App stores to do this for me which eliminates the need for me to handle transactions and licensing. I think I would need to be working on MobileSheetsPro full time for this to become an option though.
It will be your choice if you want to use the Window 10 version to manage your library, but it is not set up like the companion application. It is not designed to manage the library of an external device - it is going to be identical to the Android version in terms of functionality and behavior. If you mirror your library between your PC and your tablet, then you could use the Windows 10 version for this purpose. Once I add more synchronization features, this may become a feasible option for replacing the companion app.
If a huge demand for a Linux version develops at any point, I will certainly consider porting over the code to something like C++/wxWidgets, but I will have to figure out how to sell/license that version, as I'm currently relying on App stores to do this for me which eliminates the need for me to handle transactions and licensing. I think I would need to be working on MobileSheetsPro full time for this to become an option though.