Not sure what the state of play for this product is now, but at the time we considered it too risky a proposition (what if they go out of business tomorrow?) and too limiting for the cost they were asking to use their platform.
Their particular IDE may be closed-source, but the engine is not tied to it.
IIRC playcanvas was started by ex-mozilla people.
I played around with the engine a while ago and was quite impressed by the all-in-one-ness of it.
But, at that time it didn’t meet our requirements.
I recall our unity engineer quite liked Defold, which had an integrated builder tool, but for some reason the lead dev didn’t want to go with it.
I don’t want to be throwing shade on Play Canvas though, it’s possible if we did the same assessment today we would have gone with that engine.
We had been using Unity for a long time but when the company decided pivot to HTML, we kept running into performance issues for for web (which left the Unity developer we had hired in a pretty awkward position).
It looks like Snap bought it + a game studio and then launched a few html5 games inside of Snapchat. But I dont see anything after that. Seems like maybe gaming inside of snapchat just fizzled out? That doesn't bode well for PlayCanvas development...
A competitive FPS shooter made in Playcanvas.
Is it the JS ecosystem and [insert framework] UI that's tempting? Or just the shared dev environment?
Runescape is a good example. It ran on the school and library computers when nothing else could (much less anything that needed installation). Runescape is finally beta-testing native mobile apps, and it's hard to imagine it rising to so much fame for such a long time without its decision to run in the browser.
Unity, Unreal, Godot ... they all support the web as publishing targets. Without downloading a plugin. supporting the web is not unique. but if you design for the web, the engine will run better than compiling to it.
> Runescape is finally beta-testing native mobile apps, and it's hard to imagine it rising to so much fame for such a long time without its decision to run in the browser.
They've had a mobile version of "Old School Runescape" for over a year now I think, and it certainly did get me to play again for a bit. Mostly out of a curiosity of how they managed to fit all that UI on a mobile screen (turns out, pretty well).
The blog is 4 years old but I think it's still relevant.
I think partially it's that once you are doing something at this level, you are no longer just turning a document into an app, you are writing an app that can be deployed almost anywhere.
I think the future will trend in this direction to be honest.
edit: tend -> trend