When comparing Moai SDK vs Phaser.io, the Slant community recommends Phaser.io for most people. In the question“What are the best 2D game engines?” Phaser.io is ranked 8th while Moai SDK is ranked 19th.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Fast
Because it uses Lua + C++.
Pro Gives you total control
You can use your own custom shaders and extend the language with C++. MOAI doesn't give you everything, instead it gives you the tools you need to develop any game you want.
Pro Full source code is available
So it is extendable with C++
Pro Easy-to-use particle engine
Uses a limited subset of Lua
Pro Uses Lua, with LuaJIT where possible

Pro Is used by many pro developers
Moai SDK is used by popular developers including Double Fine for their mobile game, Middle Manager of Justice, and for their Kickstarter hit, Broken Age(formerly, Double Fine Adventure.) It was also used to create the popular mobile game Bubble Ball 2.
This proves that this engine can be used to make fully-featured and fun games.

Pro API interfaces
Has options for development like Hanappe and Rapanui, providing a different way to interact with the engine.
Pro Helpful community
The Moai SDK Forum is active and users will go to great extents to answer queries, post code snippets, beta test, and even purchase and give feedback on each others' games.
Pro Helpful and detailed documentation
Although the Moai SDK is very advanced and uses complicated features, the documentation wiki thoroughly and clearly explains how to use these features, such as the Moai Cloud(a service that provides web services for your game), and multiple ways to build from source.
Pro Great community resources
Pro Built-in Arcade Particle system
Pro Very active development
This is one of the most developed frameworks right now.
Pro WebGL and Canvas rendering modes
You can choose WebGL or classic HTML canvas element for game rendering.

Pro Good tutorials, courses and books
There are plenty of great learning resources available for Phaser.io.
Pro Super-simple loading of assets
Pro Excellent tools for sprites
Pro Support for Arcade Physics, Ninja Physics and p2.js
Pro Easy to learn
Most tasks are done just using 2 or 3 lines of code.


Pro Very fast to develop with
If you're browsing Slant, you probably already have a JavaScript enabled browser, which is most of what you need to get started learning JavaScript. The requirement to run a server locally on your computer while developing might make things a little more difficult
Pro No install required
All you need to do is attach Phaser script to a HTML page even without installing any extensions.
Pro Easy to understand if you have used flash
Phaser provides a similar approach as to that of Flash games, where you can load assets and place them on a stage, and even improves upon the shortcomings of actionscript. It is very easy to shift from flash to HTML5 development because of this approach.
Pro You can run it in the cloud
You can use it in popular online editors like replit, codandbox, etc.
Pro Animating is easy
Pro Has separate versions maintained by developer and the community
The creator of phaser(photonstorm) has given the older(Phaser 2.0) source code to the community for their own maintenance, and has made Phaser 3.0 with a different style and approach, trying to make it easier for beginners to learn.
Cons
Con Not for beginning developers
The Moai SDK has very advanced features which allow it to create powerful games. A drawback from this is that it is not very suitable for beginners.
Con Not necessarily tested or stable

Con Scarce documentation
Since it is a minimalist framework there is not that much documentation, but if you are used to reading API references and source code you are good to go!
Con Development has ceased
The last update was over a year ago. Users should not expect things to still work on future OS versions unless they're ready to fix them yourself.
Con Using Cordova to Export for Mobile
To export to mobile games you need to use cordova.
Con Official documentation is not so good

Con Poor performance
As long as your map is not larger than 600*400px, everything is fine.
Con Extremely many bugs
Con Developer ignores community needs
