Looking for planning advice on porting MacOS app to Windows 10

  architecture, graphics, native, port, windows

I am developing an application on my Mac in C with a Swift layer for the GUI using Xcode. It is clear to me that a significant portion of my user base is using Windows 10 so I want to build a version that runs natively on windows. I am looking for some advice about technology and design decisions. The project is an engine for data-processing, rendering and code execution a little like a scaled back VM. I don’t expect complete answers, but if anyone could look at this and address any part of it, it could be a big help.

I have a few considerations:

  1. I want to avoid as many surprises as possible. I’m concerned about the need to update elements other than the C code, poor documentation of the development process and broken or finicky packages to install, etc. I have installed one too many broken packages on *nix systems with recursive dependencies that are sometimes themselves somehow broken.

  2. The C code will do most of the calculations, but I need to be able to display pretty much whatever it is through the GUI. If it matters I’m looking to render, display and play all sorts of audiovisual rendering by calling the C libraries from the GUI. Outputs on the GUI could be graphs, text, video, audio effects and files or even 3D animation that updates synchronously or asynchronously.

  3. The system uses a database consisting of a folder of binary files, where should I store those so users don’t accidentally delete, move or alter them?

  4. I looked into Visual Studio community edition, but it’s not clear if that’s my best option. Thoughts on IDEs?

  5. Is there some angle I’m missing here?

Source: Windows Questions

LEAVE A COMMENT