<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>PRODUCTS on Flowing Code</title><link>https://www.flowingcode.com/en/category/products/</link><description>Recent content in PRODUCTS on Flowing Code</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 26 Aug 2026 15:16:17 +0000</lastBuildDate><atom:link href="https://www.flowingcode.com/en/category/products/index.xml" rel="self" type="application/rss+xml"/><item><title>Introducing AppJars: Production-Ready Modules for Java Enterprise Applications</title><link>https://www.flowingcode.com/en/introducing-appjars-production-ready-modules-for-java-enterprise-applications/</link><pubDate>Tue, 25 Aug 2026 20:48:23 +0000</pubDate><guid>https://www.flowingcode.com/en/introducing-appjars-production-ready-modules-for-java-enterprise-applications/</guid><description>&lt;figure class="wp-block-image size-large">&lt;img alt="" class="wp-image-2496" height="585" loading="lazy" src="https://www.flowingcode.com/images/uploads/2026/08/Introducing-AppJars-1024x585.png" width="1024"/>&lt;/figure>
&lt;p class="wp-block-paragraph">Over years of building enterprise applications for clients across many industries, we kept running into the same thing. Before a team can write the part that makes an application unique, it spends weeks, sometimes months, rebuilding the same foundations: user management, audit trails, reporting, translations, email, background jobs. Necessary work, and rarely the reason the project started.&lt;/p></description></item></channel></rss>