One of the advantages of using Mendix is that business-oriented people can learn how to create an application. It is not required to be a computer scientist to know how to work with Mendix. This makes the pool of potential Mendix developers much larger than traditional developers. However, there are common characteristics between a traditional and Mendix development team that should not be overlooked. In this article, Menno de Haas, Team Lead at WebFlight, discusses a number of aspects that are essential for a high-quality output of a Mendix development

As an enthusiastic App Store publisher, I just published a new version of the JWT and Queue module. I clicked around to see how much the modules were downloaded, which gives a good impression of the value and popularity of the modules. I was happy that they passed the 100 downloads. Then I came across the Cat Connector (https://appstore.home.mendix.com/link/app/3049/TimeSeries/Cat-Connector), which was downloaded 126 times. Suddenly I was blown away by the creativity my limited brain capacity could not grasp. How could something completely useless like an implementation of TheCatAPI.com get

A few months ago I posted a new module in the Mendix App Store, called  the Queue module. In this blog I will take you through the development process and elaborate on the design trade-offs that resulted in a Queue that is 7,4 times faster than the Process Queue. So no high level talk, let’s take a deep dive!