<?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"><channel><title><![CDATA[InteeBuild]]></title><description><![CDATA[InteeBuild]]></description><link>https://inteebuild.hashnode.dev</link><image><url>https://cdn.hashnode.com/uploads/logos/6ac3f3967d3cc669fdd27cad/2843c930-6322-4caa-8c56-c2f2f1ec33da.png</url><title>InteeBuild</title><link>https://inteebuild.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Mon, 12 Oct 2026 12:27:29 GMT</lastBuildDate><atom:link href="https://inteebuild.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[I Built an Open-Source Tool That Turns Websites Into Android Apps
]]></title><description><![CDATA[I Built an Open-Source Tool That Turns Websites Into Android Apps
Hey everyone!
I’ve been working on a project called InteeBuild.
The idea is pretty simple:

Give it a public website or HTML and get a]]></description><link>https://inteebuild.hashnode.dev/i-built-an-open-source-tool-that-turns-websites-into-android-apps</link><guid isPermaLink="true">https://inteebuild.hashnode.dev/i-built-an-open-source-tool-that-turns-websites-into-android-apps</guid><category><![CDATA[Open Source]]></category><category><![CDATA[Android]]></category><category><![CDATA[compiler]]></category><category><![CDATA[webdev]]></category><dc:creator><![CDATA[Guillermo Rafael]]></dc:creator><pubDate>Mon, 05 Oct 2026 19:05:09 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6ac3f3967d3cc669fdd27cad/8ec51ab1-325e-4c59-bac9-b23288c8b50f.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h1><strong>I Built an Open-Source Tool That Turns Websites Into Android Apps</strong></h1>
<p>Hey everyone!</p>
<p>I’ve been working on a project called <strong>InteeBuild</strong>.</p>
<p>The idea is pretty simple:</p>
<blockquote>
<p>Give it a public website or HTML and get an Android project/APK/AAB without having to manually set everything up.</p>
</blockquote>
<p>GitHub:<br /><a href="https://github.com/Fluxionics/InteeBuild">https://github.com/Fluxionics/InteeBuild</a></p>
<h2><strong>What can it do?</strong></h2>
<p>InteeBuild currently supports things like:</p>
<ul>
<li><p>Website → Android app</p>
</li>
<li><p>HTML → Android app</p>
</li>
<li><p>APK / AAB builds</p>
</li>
<li><p>Custom app name and package</p>
</li>
<li><p>Custom icons</p>
</li>
<li><p>Android permissions</p>
</li>
<li><p>Background audio</p>
</li>
<li><p>Native bridges</p>
</li>
<li><p>GitHub Actions builds</p>
</li>
<li><p>Build artifacts</p>
</li>
<li><p>Build logs</p>
</li>
<li><p>API access</p>
</li>
<li><p>Webhooks</p>
</li>
<li><p>APK inspection/decompilation</p>
</li>
<li><p>Security checks for URLs and webhooks</p>
</li>
</ul>
<p>One of the parts I spent the most time on was the permission system.</p>
<p>Instead of simply adding permissions to the manifest, InteeBuild keeps information about whether a permission requires runtime access, special Android settings, dependencies, minimum SDK versions, etc.</p>
<h2><strong>Security</strong></h2>
<p>Since the server can receive URLs and APK files, I also added protections against things like:</p>
<ul>
<li><p>SSRF</p>
</li>
<li><p>localhost/private IP access</p>
</li>
<li><p>cloud metadata endpoints</p>
</li>
<li><p>malicious ZIP/APK structures</p>
</li>
<li><p>oversized inputs</p>
</li>
<li><p>API abuse</p>
</li>
<li><p>invalid webhooks</p>
</li>
<li><p>rate-limit abuse</p>
</li>
</ul>
<p>There are also automated tests for many of these cases.</p>
<h2><strong>Why did I make it?</strong></h2>
<p>I wanted something that could take a website and make the Android side much less annoying.</p>
<p>There are already many tools that do something similar, but I wanted InteeBuild to be more transparent about what is actually generated and what still requires native implementation.</p>
<p>For example, adding a permission to Android's manifest doesn't magically make the website capable of using that hardware.</p>
<p>So the project tries to distinguish between:</p>
<p><code>declared → supported → generated → actually usable</code></p>
<h2><strong>What's next?</strong></h2>
<p>Right now I'm focusing more on stability and security instead of just adding more features.</p>
<p>I want the core pipeline to be reliable:</p>
<p><strong>URL/HTML → Analyze → Configure → Audit → Build → APK/AAB</strong></p>
<p>I'd love to hear feedback from other developers.</p>
<p>GitHub:</p>
<p><a href="https://github.com/Fluxionics/InteeBuild">https://github.com/Fluxionics/InteeBuild</a></p>
]]></content:encoded></item></channel></rss>