How easily could a Mendix Developer transfer the skills of Rapid App Development to another tool in Gartner’s Magic Quadrant for hpaPaaS? I look at OutSystems to help answer that question.
Last week, I along with other leaders in our Rapid App Dev practice joined Mendix in Rotterdam for their #MxWorld2019 event. If you’ve read my other posts, you’ll get a more play by play take on the event and the activities my teammates and I participated in leading up to, during, and after the event. I’ve had a few days to step back and reflect on the event and wanted to share my Top 5 takeaways with you. Let me know if you agree or had a different key takeaway (not surprising if you did as there were many announcements!)
It’s been 1 year since I first wrote the post, “Extending SAP: Fiori or Mendix?” and a lot has changed. Because of the changes, this older post has gotten a lot of renewed interest so I thought I would take a look at my opinions from a year ago and see if they differ. If you haven’t already, please refer to the original article to have context for this one.
IT should be an expert “SWAT” team with precise skills to tackle the toughest app challenges, not a bottleneck to solving business problems.
“With SAP tools like Fiori and UI5, why would I need Mendix?”
As a practitioner who directs our architecture and development of Mendix applications alongside SAP developers, I get asked this question a lot. Rapid Application Development (RAD) tools like Mendix are on the rise because as businesses begin their journey into digital transformation, they realize that the agility necessary to respond to rapidly changing competition and value perceptions require focused teams that combine business leadership and IT to design and deploy solutions just as rapidly. Waiting for a waterfall, stack-developed project to get scoped and developed will typically miss the mark, come out behind the curve of the transformation, and be dead in the water by the time it hits the market or the business.
Let’s face it: Application Security Modeling is a difficult topic. I’ve seen (and built) numerous attempts and security models using the Mendix framework, and they are rarely consistent and often misunderstood. I’m going to attempt to document my processes and procedures that I have determined to be best practices to hopefully help some developers out there struggling to find a “best practice security Mendix” search on Google. There are many ways to approach it so by no means is my approach the only way to do this, but I do know it works to ensure each element is considered in the modeling
I’d like to share some knowledge I picked up along the way when working to deploy a Mendix app with custom widgets that required a build in PhoneGap (not the standard “Publish” method in the Mendix Dev Portal) and the steps not articulated in the current guide as a supplement to help anyone else with some of the steps I initially struggled with. Hopefully it saves others the trials and time it took me to figure out.