<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Thijs de Jong on Medium]]></title>
        <description><![CDATA[Stories by Thijs de Jong on Medium]]></description>
        <link>https://medium.com/@thijs.de.jong?source=rss-fec25cf085b4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*Eed8vblrnRMF0aCyl1LFTA.jpeg</url>
            <title>Stories by Thijs de Jong on Medium</title>
            <link>https://medium.com/@thijs.de.jong?source=rss-fec25cf085b4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 00:25:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@thijs.de.jong/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Mitigating Risk in Mendix Applications]]></title>
            <link>https://medium.com/mendix/mitigating-risk-in-mendix-applications-7cc177236b5a?source=rss-fec25cf085b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/7cc177236b5a</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[hacking]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[mendix]]></category>
            <dc:creator><![CDATA[Thijs de Jong]]></dc:creator>
            <pubDate>Sun, 01 Mar 2026 18:25:37 GMT</pubDate>
            <atom:updated>2026-07-27T23:44:08.003Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*m6mQnnH4V-MK-fX-dcouzQ.png" /></figure><h4>A Practical Security Guide for Developers</h4><figure><img alt="A header image showing the article title." src="https://cdn-images-1.medium.com/max/1024/1*pHrhCG6Ztj_wFmLDcIsKZg.jpeg" /><figcaption>Mitigating Risk in Mendix Applications</figcaption></figure><p>Recently, the Dutch Institute for Vulnerability Disclosure (DIVD) <a href="https://www.divd.nl/mendix.html">highlighted a widespread issue</a> affecting thousands of poorly configured Mendix applications exposed on the public internet. Ethical security researchers discovered <strong>more than 2,000 instances</strong> where data could potentially be accessed without authorization, not through a flaw in the Mendix platform itself, but due to misconfigured access control settings.</p><blockquote>“The issue is primarily caused by <strong>application-level authorization misconfiguration</strong>,…”</blockquote><p>Maybe you read the DIVD article, a <a href="https://tweakers.net/nieuws/245192/divd-hackers-ontdekken-2000-slecht-geconfigureerde-publieke-mendix-installaties.html">post on Tweakers</a>, or even received an urgent email from your security officer and are thinking to yourself: “Surely my app is secure... <em>right</em>?”</p><p>Below is a comprehensive guide to the tools, tricks and best practices that we use at <a href="https://innspire.nl/">InnSpire</a> that help us gauge the security of our applications, fix common weaknesses, and adopt practices to keep apps secure. We hope that you too can use this to improve the security of your apps and the Mendix application landscape as a whole.</p><h3>Tools for analyzing your app security</h3><p>The first step to improving your app’s security is understanding roles and access rules. Because apps in Mendix consist of one or more modules, and a module typically has a functional scope, Mendix provides role-based user access to applications. Because of the distinction between apps and modules, security aspects are defined on both levels. Each access rule grants certain access rights to those roles. Rules are additive, which means that if multiple access rules apply to the same module role, all access rights of those rules are combined for that module role. This is why understanding the access you are providing to each user role is crucial.</p><p>The <a href="https://docs.mendix.com/refguide/security-overview/">Mendix Security Overview</a> provides a good first overview into your app’s security. You can also export information from the page to an Excel file which makes it great for auditing purposes.</p><p>The <a href="https://ciphix.io/en/service/devtools-for-mendix/">Ciphix Mendix Dev Tools</a> browser plugin is a great tool for gaining insight into which objects the current user has access to by making use of the exposed REST API. Beyond that it has performance tools that can record application activity in the client and on the server.</p><p><a href="https://portswigger.net/burp">Burp Suite</a> is a security testing tool that acts as a proxy between your browser (or mobile device) and the server. It allows you to capture, inspect, and modify network traffic in real time. In practice, this means you can see exactly which requests your Mendix app sends, what parameters are included, and what data the server returns.</p><p><a href="https://medium.com/mendix/inspecting-https-traffic-from-a-mendix-native-app-c6818ebe38ef">Inspecting HTTPS traffic from a Mendix Native App</a></p><p><a href="https://menscan.io/">Menscan.io</a> is another great tool that provides system analysis, vulnerability detection and metadata extraction such as user permissions and database structure.</p><p>One of the DIVD’s ethical hackers has also shared their own tool: <a href="https://github.com/Jelle-DIVD/MendixHunter">MendixHunter</a>. While we’ve not had the chance to use MendixHunter extensively in the field yet it does seem to be a potent tool for security research with features to scan available API’s, intercept microflows and inject custom code.</p><figure><img alt="An image showing the DIVD MendixHunter tool" src="https://cdn-images-1.medium.com/max/1024/1*INhyg2aEuWA8h_NX_D8r1Q.png" /><figcaption>The DIVD MendixHunter tool</figcaption></figure><p>All of these tools are great for finding misconfigured access control settings and other security risks. But make no mistake: the only way they will have impact is if they are embedded into a structured software development life cycle. Thorough peer review, manual/automated testing and continuous security validation throughout design, development, and deployment are what ultimately turn security tooling from an occasional thing into a meaningful risk-reduction strategy.</p><h3>Tools for enforcing security best practices</h3><h4>MxLint</h4><p><a href="https://mxlint.com/">MxLint </a>is an analysis tool for Mendix that scans your app model for quality, maintainability, and security issues. It analyzes elements like domain models, microflows, and access rules to detect risky patterns before they reach production.</p><p>It is available as a CLI, making it easy to integrate into CI/CD pipelines, and it can also be added to a Mendix project as a custom extension for in-project validation. MxLint comes with a (admittedly small as of now) set of standard rules out of the box, but it can be fully customized to align with your own development standards and coding guidelines. Updates are frequent so we’re interested to see how this tool develops.</p><h4>Strict mode</h4><p>Enabling <a href="https://docs.mendix.com/refguide/strict-mode/">Strict Mode</a> (a feature exclusive to the React client introduced in Mendix 10.12) adds an extra layer of protection by tightening how the client can interact with your data. When Strict Mode is active, entities can only be accessed in the ways you’ve explicitly defined in your model: through microflows, nanoflows, pages, or widgets. Direct client-side access through certain APIs is restricted, reducing the risk that a misconfigured access rule results in unintended data exposure.</p><p>In other words, Strict Mode helps ensure that your application behaves exactly as modeled and nothing more. Strict mode is not a replacement for well configured access rules, but it is a safety net.</p><h3>Tips and tricks for app security</h3><h4>Treat anonymous users as internet traffic</h4><p>If you enable anonymous access, assume the entire internet is your user base. Limit entity access strictly and never expose business data without tight XPath constraints.</p><h4>Never rely on page visibility for security</h4><p>Hiding a button or page does not secure the data. Always enforce security at the entity level and inside microflows.</p><h4>Review “Apply Entity Access” in microflows</h4><p>If unchecked, your microflow may bypass entity access rules. Only disable it if you fully understand the implications.</p><h4>Lock down published REST and OData services</h4><ul><li>Require authentication wherever possible</li><li>Carefully assign allowed roles</li><li>Validate input parameters</li><li>Avoid returning entire objects if only specific attributes are needed</li></ul><h4>Keep marketplace modules updated</h4><p>Old modules can contain outdated Java libraries or insecure patterns. Periodically review dependencies and remove unused modules.</p><h4>Log often but smart</h4><p>Enable audit logging for sensitive actions, but avoid logging passwords or tokens. When something goes wrong, thorough and descriptive logs will be invaluable.</p><h4>Review security before every release</h4><p>Make security review part of your Definition of Done:</p><ul><li>Entity access reviewed</li><li>New attributes checked</li><li>APIs reviewed</li><li>Anonymous role verified</li></ul><h4>Design for least privilege</h4><p>Start with no access, then explicitly grant only what’s required. Always set “Default rights for new members” to “None.”</p><h4>Monitor in Production</h4><p>Security isn’t finished at deployment:</p><ul><li>Watch logs for unusual query volumes</li><li>Monitor API usage patterns</li><li>Review failed login attempts</li></ul><h4>Use representative data in test and acceptance environments</h4><p>The more your data in your test and acceptance environments differs from production in scope and structure, the more difficult it is to spot misconfigured security settings. Keep these as similar as possible (though of course avoid having sensitive production data anywhere but production).</p><figure><img alt="A marketing banner for Mendix Capture the Flag 2025" src="https://cdn-images-1.medium.com/max/1024/0*IkWCYp782Yyotq_O" /></figure><h4>Attend Capture the Flag</h4><p>Attending the Capture the Flag event is a hands-on way to sharpen your security skills. By tackling real-world challenges in a safe environment, you learn how vulnerabilities appear in Mendix apps and how to fix them before they reach production. Sure, CTF 2025 was just a few months ago but this year’s will be here before you know it.</p><h3>Final thoughts</h3><p>DIVD’s recent findings aren’t a reason to panic but they are a reminder to take a closer look at how we configure our apps. Mendix is a secure and mature platform, but it follows the rules we set. If those rules are too broad, inconsistent, or left unchecked, data can be exposed unintentionally.</p><p>The good news is that these risks can be controlled. Regularly reviewing roles, enforcing entity-level access, and monitoring production activity make security part of our everyday development process, not an afterthought. By building these habits into our workflow, we ensure our Mendix apps stay safe and reliable. Remember: no security incidents mean more time to build cool features and less stressful weekends 😎🏖️.</p><p>Author:</p><p><a href="https://www.linkedin.com/in/thijs-de-jong/">Thijs de Jong</a> — Mendix MVP, Expert Consultant and Architect @ <a href="https://innspire.nl/">InnSpire</a></p><h3>Read More</h3><ul><li><a href="https://www.mendix.com/trust/handling-security-findings-related-to-data-exposure/">Handling Security Findings Related to Data Exposure | Mendix</a></li><li><a href="https://docs.mendix.com/howto10/security/best-practices-security/">Implement Best Practices for App Security</a></li><li><a href="https://the-s-unit.nl/en/the-s-unit-top-10/">The S-Unit Top 10 - The S-Unit</a></li></ul><p><strong><em>From the Publisher -</em></strong></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7cc177236b5a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/mitigating-risk-in-mendix-applications-7cc177236b5a">Mitigating Risk in Mendix Applications</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mendix Native: a Performance Optimization Guide]]></title>
            <link>https://medium.com/mendix/mendix-native-a-performance-optimization-guide-fd61ade7a57e?source=rss-fec25cf085b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/fd61ade7a57e</guid>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[react-native-app]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[mendix]]></category>
            <dc:creator><![CDATA[Thijs de Jong]]></dc:creator>
            <pubDate>Wed, 25 Jun 2025 07:37:38 GMT</pubDate>
            <atom:updated>2025-10-13T12:26:25.302Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Mendix Native: a Performance Optimization Guide — Banner Image" src="https://cdn-images-1.medium.com/max/1024/1*ePYkYIaJFMrgxvm3jw7uUg.png" /><figcaption>Mendix Native: a Performance Optimization Guide *Image generated by ChatGPT 4o*</figcaption></figure><h4>Bad performance by itself is enough to break your app’s user experience. Even more so for a customer-facing application.</h4><h4>Users expect apps to feel smooth and responsive. Even slight delays can result in frustration, bad reviews, or even uninstalls. Mendix Native gives us the ability to deliver great cross-platform apps, but it also introduces new performance considerations compared to traditional Mendix web apps that can be tricky for developers not used to this way of working.</h4><p>In this post, we’ll explore some strategies to optimize your Mendix Native app’s performance.</p><h3>What causes Mendix Native performance issues?</h3><p>Before we optimize, it’s important to understand <em>where</em> potential performance problems come from:</p><ul><li><strong>Complex associations: </strong>retrieving data through deeply nested associations.</li><li><strong>Unnecessary synchronization</strong>: synchronizing more often or more data than needed.</li><li><strong>Complex navigation stacks: </strong>stacking pages unnecessarily.</li><li><strong>Too many elements</strong>: bulky pages with deeply nested layouts</li></ul><p>The good news: most of these are avoidable with careful design. Here are some tips to improve the performance of your Mendix Native app.</p><h4>Simplify associations</h4><p>Deeply nested entity associations (e.g. Product → Order → Customer → Address → Region → Country) may look clean in the domain model but cause performance issues when fully loaded.</p><ul><li>Flatten relationships when necessary. Retrieving an object fetches associated objects as well, so it can often be beneficial for performance to store some attributes redundantly when dealing with large datasets (e.g. a CustomerId on the Order entity).</li></ul><h4>Synchronize only what is needed</h4><p>In your native mobile navigation profile, you can control what data gets downloaded to the device for offline use. Syncing unnecessary data means the app does more work than it needs to, which can impact performance, especially on lower-end mobile devices.</p><p>Every object synced:</p><ul><li>Consumes storage.</li><li>Takes memory when loaded.</li><li>Increases initial sync times.</li></ul><p>To optimize your app’s synchronization, you should:</p><ul><li>Use XPath Constraints. Apply precise filters to restrict records. For example, sync only records assigned to the current user, recent records, or active tasks. Remember that XPath constraints can also introduce performance issues when they span multiple tables. This applies to the synchronization profile and to domain model access rules.</li><li>Avoid using “Sync Everything”.<strong> </strong>Be intentional about every entity you synchronize.</li><li>A complex application will almost always benefit from a custom synchronization solution, especially apps with large datasets. An example of leveraging the “Sync to Device” synchronization mode to gain increased performance would be <a href="https://docs.mendix.com/refguide/mobile/best-practices/incremental-synchronization/">Incremental Synchronization</a>.</li></ul><figure><img alt="An image showing the Custom offline synchronization configuration screen." src="https://cdn-images-1.medium.com/max/920/1*9J5ZupPddSLkmGqGYYLHQQ.png" /></figure><h4>Keep navigation stacks small</h4><p>Every time you navigate forward, you’re adding a new page to the navigation stack. Each page in the background remains active. This can lead to unintended re-renders when data changes, which often impacts performance for large stacks.</p><ul><li>Avoid large page stacks whenever possible.</li><li>Avoid duplicate instances of the same page in the stack.</li><li>Use pop-ups or bottom sheets for temporary screens rather than full navigation pushes.</li></ul><p>Shallow stacks reduce memory usage and improve responsiveness to backwards navigation. Read more about this topic in <a href="https://medium.com/u/4ef197210ccc">Wouter Penris</a>’ blog.</p><p><a href="https://medium.com/mendix/managing-page-stacks-in-mendix-react-native-navigation-best-practices-9443fca59ee0">Managing Page Stacks in Mendix React Native: Navigation Best Practices</a></p><h4>Keep your pages small and clean</h4><p>More elements on a page mean more elements to render, which means more processing and memory use, especially for deeply nested layouts. Consider working up from the page design to the data, instead of the other way around.</p><ul><li>Break large pages up into multiple screens. Not only is this faster to render, but this can often be more user-friendly as well.</li></ul><h4>Avoid unnecessary visibility conditions</h4><p>Conditional visibility triggers re-rendering when conditions change. Use them wisely, especially inside lists or frequently updated views.</p><ul><li>This also counts for data sources. For instance, when a nanoflow datasource parameter changes, it can be retriggered, potentially causing redundant retrieves and unnecessary renders.</li></ul><h4>Be wary of network requests in nanoflows</h4><p>Nanoflows execute directly on the device, which means there’s generally no network round-trip. However, you can still add a microflow call to your nanoflow, even in a Mendix Native app.</p><ul><li>Nanoflow activities are executed sequentially. Multiple microflow calls in the same nanoflow, therefore, will result in multiple calls to the runtime. Try to bundle these actions into one microflow call.</li><li>This is also true for nanoflows used in online applications that perform multiple database-related actions.</li></ul><blockquote><strong>Tip:</strong><br>When calling a microflow from a native mobile application, first check whether a connection to the server can be made using the IsConnectedToServer Javascript action from NanoflowCommons to avoid making unnecessary calls to the runtime and presenting the user with an error. Additionally, make sure you have error handling on every microflow call in a native mobile nanoflow.</blockquote><h4>Bonus: Use view entities (Beta feature released in 10.19)</h4><blockquote>A view entity represents the result set of a stored OQL query and can be used similarly to a persistable entity. This concept is similar to the function of views in general database technology. Whenever a view entity is retrieved via a page or a microflow, the corresponding OQL query runs and fetches the relevant data. Consequently, the result set of a view entity is not stored as a separate table in the database (like a materialized view). Instead, the query runs each time the view entity is accessed, dynamically retrieving the data. -<a href="https://docs.mendix.com/refguide10/view-entities/">Mendix Docs</a></blockquote><p>Normally, in Mendix, combining data from multiple different entities (e.g., for the purpose of a dashboard) often requires complex microflows with many different object retrieves and post-retrieve calculations to bundle the data. With view entities, the database does all that work for you through OQL, resulting in:</p><ul><li>Way less data transferred.</li><li>Faster processing.</li><li>Less memory usage.</li></ul><p>You can even tell the database to pre-aggregate the data by using aggregate functions like SUM(), COUNT() and AVG() directly in your OQL query.</p><p>Unlike in a Mendix web app view entities are not refreshed every time the entity is accessed in a native app. Instead, the entity is refreshed every time it is synchronized. View entities are read-only. To change the resulting data of a view entity retrieval, the source data should be modified.</p><figure><img alt="An image of a Mendix domain model showing both regular Mendix entities and a view entity including its properties." src="https://cdn-images-1.medium.com/max/803/1*tGcJ5mL1Otl0WjSsiQ2NjA.png" /></figure><h3>Always monitor and test performance</h3><p>It’s one thing to experience bad performance and attempt to improve it. It’s another thing entirely to accurately measure performance and know exactly what’s causing it and how significant the impact of your improvements is.</p><p>Here are some tips for monitoring and testing your app’s performance.</p><h4>Use Real Devices, Not Just Emulators</h4><p>Emulators are fine for functional testing, but for real performance insights, always test on:</p><ul><li>Low-end Android devices</li><li>Older iPhones</li><li>Limited memory, lower CPU</li></ul><p>Performance issues often show up only on real-world devices. Make sure you are accurately reflecting your users’ devices when developing. Emulators do allow for easy network traffic monitoring and testing.</p><h4>Use network inspection tools</h4><p>Tools like <strong>Charles Proxy</strong>, <strong>Burp, </strong>or <strong>Fiddler </strong>allow you to:</p><ul><li>Inspect network traffic</li><li>Observe sync traffic</li><li>Detect inefficient sync profiles</li></ul><p>This is one of the best ways to spot broad queries and large data sync. Read my previous blog to learn how to set up a proxy server with Burp and gain insight into the network traffic of your Mendix Native app.</p><p><a href="https://medium.com/@thijs.de.jong/inspecting-https-traffic-from-a-mendix-native-app-c6818ebe38ef">Inspecting HTTPS traffic from a Mendix Native App</a></p><h4>Simulate bad network conditions</h4><p>Use network throttling to mimic real-world mobile conditions. A wait that might seem acceptable with your lightning-fast office internet may be less so for a user standing in a parking garage.</p><h4>Utilize online test platforms</h4><p>Cloud-based testing platforms like <a href="https://www.browserstack.com/">Browserstack </a>enable developers to test websites and mobile apps across real devices and browsers. BrowserStack supports manual and automated testing, integrates with CI/CD tools like Bitrise, and can be useful to teams without a large device lab.</p><h3>Conclusion</h3><p>Mendix Native apps require a <strong>performance-first mindset</strong>. Keep these tips in mind and you’ll deliver Mendix Native apps that feel truly native: fast, fluid, and responsive. If you have any feedback, additions, questions, or just want to have a chat about performance, native, or anything Mendix related, don’t hesitate to contact me.</p><blockquote><strong>Tip:</strong><br>Start small. Implement just 1–2 of these tips on your app and measure the difference. That way you know exactly what impact each change has.</blockquote><p><em>From the </em><a href="https://www.linkedin.com/in/thijs-de-jong/"><em>Author</em></a><em>-</em></p><p><em>My thanks to </em><a href="https://www.linkedin.com/in/jdiehl/"><em>Jonathan Diehl</em></a><em>, </em><a href="https://www.linkedin.com/in/wpenris/"><em>Wouter Penris</em></a><em>, </em><a href="https://www.linkedin.com/in/groenewegmarcel/"><em>Marcel Groeneweg</em></a>,<em> and </em><a href="https://www.linkedin.com/in/daanbest/"><em>Daan Best</em></a><em> for providing their feedback during the writing of this blog.</em></p><h4>Read More</h4><ul><li><a href="https://docs.mendix.com/refguide/community-best-practices-for-app-performance/">Community Best Practices for App Performance</a></li><li><a href="https://docs.mendix.com/refguide/oql/">OQL</a></li></ul><p><strong><em>From the Publisher -</em></strong></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fd61ade7a57e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/mendix-native-a-performance-optimization-guide-fd61ade7a57e">Mendix Native: a Performance Optimization Guide</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Inspecting HTTPS traffic from a Mendix Native App]]></title>
            <link>https://medium.com/mendix/inspecting-https-traffic-from-a-mendix-native-app-c6818ebe38ef?source=rss-fec25cf085b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6818ebe38ef</guid>
            <category><![CDATA[native-mobile-apps]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[how-to]]></category>
            <category><![CDATA[network-traffic]]></category>
            <category><![CDATA[mendix]]></category>
            <dc:creator><![CDATA[Thijs de Jong]]></dc:creator>
            <pubDate>Thu, 05 Jun 2025 07:45:20 GMT</pubDate>
            <atom:updated>2025-10-13T12:10:21.142Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Inspecting HTTPS Traffic from a Mendix Native App — Banner Image" src="https://cdn-images-1.medium.com/max/1024/1*0HNGmw0sUnpI7GsS5GbEjw.png" /><figcaption>Inspecting HTTPS traffic from a Mendix Native App *Image generated by ChatGPT 4o*</figcaption></figure><h4>How to patch your Android app to analyze the network traffic.</h4><h4>I’m not too proud to admit that I’ve occasionally been completely stumped by the behavior of one of my Mendix Native apps. Things that were performing fine on Test and Acceptance are suddenly incredibly slow on Production. A common reason for sudden slowness in Mendix Native apps is heavy network traffic, especially during (startup) synchronizations.</h4><p>When using the Make It Native app, it’s easy to inspect network traffic using a proxy server. However, sometimes you can’t reproduce the issue locally, or you might not be able to download a copy of your production database because of security/privacy reasons. In that case, inspecting the network traffic of your Native app can be tricky because the traffic to the Mendix Cloud is only accessible through HTTPS.</p><p>In this blog, I’ll teach you how to patch your Android app so it can be used for HTTPS inspection.</p><h3><strong>Requirements</strong></h3><ul><li>The .apk file of the application you’d like to inspect.</li><li>Up-to-date versions of <a href="https://nodejs.org/en/download/">Node.js</a> (14+) and <a href="https://www.oracle.com/technetwork/java/javase/downloads/index.html">Java</a> (8+) installed on your machine.</li><li>A tool that lets you set up a proxy server. I’m using <a href="https://portswigger.net/burp">Burp Suite</a> in this guide because it’s what I’m familiar with, but you can also use other tools like Fiddler, Charles Proxy, or Mitmproxy.</li><li>Install <a href="https://github.com/niklashigi/apk-mitm">apk-mitm</a> using npm install -g apk-mitm . This is the tool we’ll be using to patch the Android app.</li></ul><h3>Step 1: Configuring your Proxy Listener</h3><p>To enable Burp to intercept the HTTP traffic generated by your Android device, you need to configure a proxy listener and bind it to an open port.</p><figure><img alt="An image showing the screen where you can configure the Burp settings for a proxy" src="https://cdn-images-1.medium.com/max/1024/1*wecQTCinJBQlGRqZRyuxZw.png" /><figcaption>Burp Proxy Settings</figcaption></figure><ol><li>In Burp, open the <strong>Settings</strong> dialog.</li><li>Go to <strong>Tools &gt; Proxy</strong>.</li><li>Under <strong>Proxy Listeners</strong>, click <strong>Add</strong>.</li><li>On the <strong>Binding</strong> tab, set <strong>Bind to port</strong> to any available port. I’m using 8080 in this example since I’m not running any Mendix application locally at the moment, and I know it’s open.</li><li>Set <strong>Bind to address</strong> to <strong>All interfaces</strong>.</li><li>Click <strong>OK</strong> and confirm your entries when prompted.</li></ol><h3>Step 2: Configure your device to proxy traffic through Burp</h3><ol><li>On your Android device, go to the network and internet settings.</li><li>Open the network details for the Wi-Fi network that you’re using.</li><li>Enter edit mode.</li><li>In the advanced settings, choose the option to configure a proxy manually.</li><li>Set the <strong>Proxy hostname</strong> to the IP Address of the machine you’re using to run Burp. You can find this IP Address by using ipconfig in the command line on the machine running Burp and checking what your IPv4 Address is.</li><li>Set the <strong>Proxy port</strong> to the port you assigned to the new proxy listener you configured in Burp.</li><li>Save your changes and then connect to the Wi-Fi network. Your device’s web traffic is now proxied through Burp.</li></ol><h3>Step 3: Add Burp’s CA certificate to your device’s trust store</h3><p>Each installation of Burp has its own built-in certificate authority (CA). To work with any HTTPS traffic in Burp, you need to add the associated CA certificate to your device’s trust store.</p><ol><li>In Burp, open the <strong>Settings</strong> dialog.</li><li>Go to <strong>Tools &gt; Proxy</strong>.</li><li>Under <strong>Proxy Listeners</strong>, click <strong>Import / export CA certificate</strong>.</li><li>In <strong>CA Certificate</strong> dialog, select <strong>Export &gt; Certificate in DER format</strong> and click <strong>Next</strong>.</li><li>Enter a filename and location for the certificate. Note that you need to explicitly include the .der file extension.</li><li>Click <strong>Next</strong>. The dialog indicates that the certificate was successfully exported.</li><li>Transfer the certificate file to your Android device.</li><li>Now you need to add the certificate to the trust store of your Android device. This process can be different depending on your device and Android version. I’ve described the process below for my device. Yours may be different.</li><li>Go to <strong>Settings &gt; Security and privacy &gt; More security settings</strong>,<strong> </strong>then select “<strong>Install from device storage</strong>” under the “<strong>Credential storage</strong>” section. Select “<strong>CA certificate</strong>”, click “<strong>Install anyway</strong>” if you get a security prompt, and then select the certificate you transferred to your device.</li><li>Your CA certificate will now be installed.</li></ol><h3>Step 4: Patching your Android app</h3><ol><li>Patch the APK using apk-mitm &lt;path-to-apk&gt;</li><li>Install the patched APK on your Android device.</li></ol><figure><img alt="An image showing the apk-mitm command being executed in PowerShell" src="https://cdn-images-1.medium.com/max/1024/1*VVylPSrSi_i-uIrVjkaJng.png" /></figure><h3>Step 5: Analyzing network traffic</h3><p>We’re finally done. Congratulations on getting this far. 🎉</p><figure><img alt="An example of a request from the patched Mendix Native APK" src="https://cdn-images-1.medium.com/max/1024/1*rywsHWa8lOHBfoeI5cy_TA.png" /><figcaption>An example of a request from the patched Mendix Native APK</figcaption></figure><p>If you’ve configured everything correctly, you should start seeing the network traffic of your patched app show up on your proxy listener in Burp. Now you can see exactly what data is being retrieved and sent by your application and use this to further analyze your app. This makes it easier to see when and where you may be sending more (or different) data over your network than you intended.</p><p><em>From the </em><a href="https://www.linkedin.com/in/thijs-de-jong/"><em>Author</em></a><em>-<br>I’d like to thank Arjen Lammers from Mendix for first showing me that this was possible and sharing his knowledge on the apk-mitm tool.</em></p><h4>Read More</h4><ul><li><a href="https://portswigger.net/burp">Burp - Web Application Security, Testing, &amp; Scanning - PortSwigger</a></li><li><a href="https://github.com/niklashigi/apk-mitm">GitHub - niklashigi/apk-mitm: 🤖 A CLI application that automatically prepares Android APK files for HTTPS inspection</a></li></ul><p><strong><em>From the Publisher -</em></strong></p><p><em>Inspired by this article to bring your ideas to life with Mendix? Sign up for a </em><a href="https://signup.mendix.com/?utm_medium=content_syndication&amp;utm_source=medium.com&amp;utm_id=11172331"><em>free account</em></a><em>! You’ll get instant access to the </em><a href="https://academy.mendix.com/link/home"><em>Mendix Academy,</em></a><em> where you can start building your skills.</em></p><p><em>For more articles like this one, visit our </em><a href="https://medium.com/mendix"><em>Medium page</em></a><em>. And you can find a wealth of instructional videos on our </em><a href="https://www.youtube.com/c/MendixCommunity/community"><em>community YouTube page</em></a><em>.</em></p><p><em>Speaking of our community, join us in our </em><a href="https://join.slack.com/t/mendixcommunity/shared_invite/zt-hwhwkcxu-~59ywyjqHlUHXmrw5heqpQ"><em>Slack community channel</em></a><em>. We’d love to hear your ideas and insights!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c6818ebe38ef" width="1" height="1" alt=""><hr><p><a href="https://medium.com/mendix/inspecting-https-traffic-from-a-mendix-native-app-c6818ebe38ef">Inspecting HTTPS traffic from a Mendix Native App</a> was originally published in <a href="https://medium.com/mendix">Mendix Community</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>