Desktop version?
- Thread starter 大卫
- Start date
Not officially, but some users have had success running our Android app in various emulators on desktops, and newish Chromebooks support running Android apps officially through the Play Store so if you consider those to be 'desktops' that would be a desktop version.
Also, we are hoping to launch a macOS app later this year when Apple releases a macOS update with their new "Project Marzipan" allowing iPad apps to be easily recompiled to work on Mac.
Also, we are hoping to launch a macOS app later this year when Apple releases a macOS update with their new "Project Marzipan" allowing iPad apps to be easily recompiled to work on Mac.
Initially, yes - it's way, way easier to port an iOS app to Mac than to port an iOS or Android app to Windows. (our understanding is that a basic Mac port with Marzipan will pretty much just involve checking a box in Xcode and rebuilding) In fact there's a pretty good chance that 4.0 will be out on Mac before it's even out on Android 
We might consider a Windows port if the Mac app is a big success, the main question is how we pay for it - we aren't confident that enough people would buy our app on Windows to pay for the cost of that port. We've toyed with the idea of doing it as a Kickstarter, actually - that would be a good way to see if there was enough interest.
We might consider a Windows port if the Mac app is a big success, the main question is how we pay for it - we aren't confident that enough people would buy our app on Windows to pay for the cost of that port. We've toyed with the idea of doing it as a Kickstarter, actually - that would be a good way to see if there was enough interest.
We’d basically have to rewrite it in scratch, since most of our engine code is in C and that’s not really viable as a web programming language unless you’re an utter lunatic
We might consider doing a putative Windows port in a cross-platform framework that also supported Linux, though - the main question would be whether there were any Windows-specific features that would be complicated by that.
We might consider doing a putative Windows port in a cross-platform framework that also supported Linux, though - the main question would be whether there were any Windows-specific features that would be complicated by that.
Good for use cases like theirs - where you have performance-intensive native code that needs to run on the front end - but wouldn't do much for us since this is mostly backend code; our UI's are written in Objective-C and Java and a putative web-based one would presumably be written in JavaScript, but the Pleco backend is all in C and that's simply not safe enough to use on a server.
I don't believe it's possible to write a Chrome plugin that uses native C either, sadly.
It would not be too difficult for us to make a desktop app with an embedded web browser once we were developing a desktop app anyway, though - indeed I expect our Mac app will include one because it's something we already support on iOS.
It would not be too difficult for us to make a desktop app with an embedded web browser once we were developing a desktop app anyway, though - indeed I expect our Mac app will include one because it's something we already support on iOS.