I assume it uses Cura as its engine, it is not open source despite that there is a github page.  

Link to AppStore:

https://apps.apple.com/app/id1614819811

Link to GitHub:

https://github.com/p3d-dev/Print-To-3D

On the subject of open source, yer it's open source but it's got Joe's name on it, it's problably as much work to audit the code of some unknown bloke than to write it yourself.

The real measure of how much support there is for an iOS would be if a project appeared on Github to fork PS. Prove me wrong.

At which point the long term effort is adding 1 platform and removing another + a little additional effort.

Alternatively, update the UX library to something that supports more target platforms which would make it possible to maintain a single code base instead of having a fork.

Projects like VLC switched to QT because of challenges with wxWidgets. There’s also Flutter from Google as another.

And yes, of course, either of these would add additional resources and cost and take time. However, PrusaSlicer is open source and surely there are people in the Prusa community and the larger printing community who might contribute, if such an effort were initiated by Prusa. 

> As I mentioned previously in this thread, and it is only MORE true now, an iPad app and a Mac App can be built from the same code base and UX.

but then you also wrote:

> I don't think creating an iOS version is inherently difficult if wxWidgets is sufficiently mature on iOS. Even if it isn't, the majority of the work would be on the wxWidgets library, not on PrusaSlicer itself. Keeping the versions in sync shouldn't require a huge amount of work, unless you decide to remove wxWidgets and call native UI APIs on iOS. That's not to say that the UI would feel GOOD on iOS, it might be a bit clunky and too "desktop", especially if wxWidgets is immature on iOS. 

While it is all true, it says nothing about the effort of each of the tasks required. There is no wxWidgets support of iOS, we don't think there ever will and we don't have the resources to write iOS support for wxWidgets. We believe that the easiest would be to ditch wxWidgets on iOS, which means a complete UI rewrite.

As I mentioned previously in this thread, and it is only MORE true now, an iPad app and a Mac App can be built from the same code base and UX.

Apple has made the tools required to have a single code base that works on both platforms.

A first step could even be to only support mouse and keyboard on the iPad which all iPads are now capable of.

Android and Windows (and Linux) are not the same. Integrated stack. An Android port is 100% a new platform, but an iPad App is not.

Pretty please Mr. Prusa by all means port to similar hardware but once you go down Android/iOS/whatever you start the inevitable slide into neither chalk nor cheese and nobody will be happy.

Vojtěch Bubník on Twitter: "@ikb3d @Bryan_Vines We are actively investigating the options. As you commented, the tablet port would require a UI revamp, thus a lot of short and long term investment, maybe hiring another developer with iOS skills, another one with Android skills to be allocated for the tablet builds." / Twitter

Posted by: @strgermishuys

Is there any new updates about having a App slicer in the upcoming future? Really like to just work off a ipad and not have to grab my laptop when downloading and slicing files to print.

 

thanks.

thanks.