Why Moxly framework is better to use for mobile app development than simple mobile app builders
Moxly is aimed at people without technical skills and offers software with No Code and Low Code, and there is an open source solution for developers. The prefix "Micro" in relation to the Moxly framework means that the framework only takes on routing (mapping paths with handlers) and helps with the formation of simple answers
Moxly allows you to create the following applications from a single code base:
I'm always cautious about writing these kinds of articles because I don't want to contribute to the overall noise and unproductive arguments of framework wars.
It is my opinion that different tools are suited to different tasks, teams, and developers. I think people should use the tool or tools that work for them and try not to mix their identity and self-worth into the tools they are using. In most cases, I think there are far bigger concerns that determine the success of an application than whether you use Ionic, React Native, Flutter, Objective-C/Swift, Java/Kotlin, or something else to build the application.
So, after sharing some brief information about Moxly, I would like to provide some justification for why I think the framework is so good.
The main core of the platform is provided free of charge with open source on github. Anybody around the world can start creating mobile apps no matter what their circumstances as long as they have a computer and an Internet connection.
Moxly strives to equalize the rules of the game and allows almost anyone to create things that can change his life and the lives of other people. If you had to pay $1,000 for a license just to start using this framework, then many developers or potential developers would never even be able to get started. A few thousand for a license does not mean anything for a large company, but for a freelance developer, a small startup or just an amateur without a large disposable income, this may be the difference between whether he can do it or not.
Moxly is owned by Nwicode Inc. — this is a real business with shareholders, which should bring money, and it should be. If someone creates some kind of tool or service that they want to charge for, then they should do it. Moxly also has commercial licenses with advanced features, which allows the platform to develop faster. But I think there's a lot of power in reducing barriers to entry as much as possible, whether it's creating a project completely free and monetizing through other means, or just creating affordable plans for small developers.
One concern when it comes to open source is stability. People worry about open source projects being abandoned, and since there is no direct revenue from the product this can quite often be the case. But when talking about projects like Moxly, which have a lot of investment dollars and many avenues to create revenue, they are no more likely to go belly up than an enterprise-focused company charging big bucks for their product.
Just because it is a big framework and is backed by Google, it doesn't necessarily mean it's the best for every situation or even in general – but with so many developers using it and the fact that there's a bunch of super smart engineers building and maintaining it, it is a pretty safe bet.
So why is our choice of Ionic and Angular frameworks for creating Moxly, because Ionic is built on Angular is good?
Here are a few reasons:
This includes components like:
As well as being free from the whims of an external company that controls the distribution of your application, we should also consider our reliance upon the company that has created the tool that we are using to build the application. What if the tool or framework you are using to build your applications suddenly decides to go in a different direction, perhaps changing their licensing model or drastically increasing prices? What if the company goes completely bankrupt, will the tool/framework continue to be maintained? Will you still be able to use it? Are the skills you have developed specific to just that one tool, or could you use what you have learned from using that tool and more easily use a new tool or approach?
This probably isn't too much of a concern if you are using the native language of the device to develop applications (i.e. Objective-C/Swift for iOS or Java/Kotlin for Android). It is something you should consider if you are relying on an external tool/framework to build your application like Ionic, React Native, Xamarin, Flutter, or anything else.
But, nothing is impervious to the various factors that influence life and business. Even the popular Parse platform which had the backing of Facebook shut down unexpectedly leaving thousands of developers in the lurch. I think this is much less likely to ever be the case for Moxly since Moxly is the company's business, whereas Parse to Facebook is not its primary business interest. But it needs to be considered.
What if next week the Moxly team in its entirety were to be suddenly abducted by aliens or some kind of malevolent cosmic artificial intelligence. What would happen to those of us who rely upon Moxly to build our applications?
This, again, is where Moxly provides a big advantage.
If the entire Moxly team were to disappear, in the short term, it would have almost no impact. All of Moxly's components are MIT licensed, open source, web components. There is no services, or renderers, or compilers, or any other dependencies required to run Moxly applications that would disappear along with the Moxly team. We can just use these components in a web-based application in any way we like.
Have you used Moxly? Let us know what you think of it, and if you haven’t used it yet it’d be great to hear your first impressions.