When comparing Felgo (formerly V-Play) vs Polymer, the Slant community recommends Polymer for most people. In the question“What are the best frameworks for developing cross-platform mobile apps with JavaScript?” Polymer is ranked 11th while Felgo (formerly V-Play) is ranked 16th. The most important reason people chose Polymer is:
It provides a base component.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Mature cross platform IDE
Qt-Creator IDE with Code Completion, Debugging and Profiling, integrated Quick Help, Version Control and more.
Pro Easy to learn
Felgo is among the easiest cross-platform tools to use according to a survey done by research2guidance.
Pro In-game level editor
With the Level Editor components, you can let your players share their levels with the whole game community which is cool because you don't need to create new levels on your own, but the community helps you with it. There are other community features like rewards for good level creators that helps getting more downloads.
Pro Felgo game network
Leaderboards, Achievements, Challenges are available across platform, even on Desktop. You can also use Cloud Syncinc of your game data that makes it easy to start a game for example on iPhone and then continue on a Nexus Tablet or the other way around.
It is also convenient because sharing to all kind of game services & networks like Facebook & Game Center is possible with a single API call. Custom hosting of Game Network servers is also possible if you want to keep the player data.
Pro Native performance
Although game logic is provided in JavaScript by you, performance-critical parts of the engine like OpenGL ES rendering or particle effects are implemented in rock-solid C++, providing the ultimate performance your game deserves.
Pro Advanced gaming components
Advanced Gaming Components for handling multiple display resolutions & aspect ratios, animations, particles, physics, multi-touch, gestures, path finding and more.
Pro Felgo build server
No need for native SDKs, Build in and Install from Cloud with the Felgo Build Server.
Pro Rapid development
Cut your development time in half. Using the QML language allows for some powerful features that cut code lines and time. Another helpful feature that can help in this area is that there are more than 50 game demos of all genres that come with full source code, meaning one can easily check to see how something was done.
Pro Support can be found in forums and via e-mail
Felgo has friendly forums where core developers participate as well as fast & helpful email support.
Pro Based on Qt framework
The Qt framework is a great and mature framework on its own. Using Qt as a game engine base is a smart idea.
Pro Runtime-balancing
You can use ready-made components to balance any of your game properties at runtime, so also on mobile devices which is great for adjusting forces or input parameters.
Pro Lots of learning resources
Helps get started and improve with lots of tutorials, demo games, examples.
Pro Social services and monetization
In-app purchases, game and social network integration (such as Game Center and Facebook), ads (with Chartboost and AdMob) and analytics (such as Flurry) are all available across platforms.
Pro Frequent updates
Every 2-4 weeks new updates provide additional features and fixes based on what users wanted the most.
Pro Level store
You can even monetize these user-generated levels with in-app purchases with the Felgo Level Store component if you like.
Pro Various basic components
It provides a base component.
Pro HTML markup is not string
HTML markup as it can be a non-string.
Pro Flex layout components
It provides Flex layout components.
Pro CSS is easy to apply
CSS can be applied far more comfortably than React.
Pro No need for special debugging tools
The presence od specialized debugging tools are advertised by competitors. The all features of web components are natively supported by browser embedded development tools.
Pro Excellent routing
The router is embedded into CLI for project creation and covers as web as Progressive web app, also fused with Polymer layouts out of the box. The shop template for CLI has a complete solution including the routing.
Pro Complete web app stack support
Full app stack from data tier to routing, progressive web app, responsive layouts makes no need to seek outside of Polymer ecosystem for application features.
In addition to waste set of mature web components in Polymer Elements along with Vaadin Elements there are thousands of web components in the wild comparable to jQuery plugins set.
Pro Excellent documentation
Polymer guides you as with tools (cli, build environment, app templates,..) as with complimentary documentation on all phases of app development from creation of app as progresive web app to production deployment instructions.
As Polymer is standards based, the whole community around those standards also helping in documentation and support.
Pro Based on web components
Web Components are a collection of specifications released by W3C as a way to reduce the complexity of web apps by creating reusable components. Browser support is currently poor for web components, however Polymer is developed to make web components compatible with modern browsers.
Pro API is easy to understand, based on standard
The Polymer APIs are split on application layers and follow standards on all possible ways: Web Components, CSS variables, async API via Promises and so on.
Cons
Con No 3rd party tutorials
There are little to none amount of tutorials for Felgo other than what was made by the engine developers themselves.
Con No server-side rendering
Polymer does not support server-side rendering. This results in higher loading times, more HTTP requests and it's not very SEO friendly, since search engines have no way of indexing a page if it's not rendered in the server.
