<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Droncito</title>
    <description>The latest articles on DEV Community by Droncito (@dron4e6h1u).</description>
    <link>https://dev.to/dron4e6h1u</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4164734%2Fb447da11-624d-4f13-b61d-44d648bb8616.png</url>
      <title>DEV Community: Droncito</title>
      <link>https://dev.to/dron4e6h1u</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dron4e6h1u"/>
    <language>en</language>
    <item>
      <title>I Built an Open-Source Tool That Turns Websites Into Android Apps</title>
      <dc:creator>Droncito</dc:creator>
      <pubDate>Mon, 05 Oct 2026 18:57:41 +0000</pubDate>
      <link>https://dev.to/dron4e6h1u/i-built-an-open-source-tool-that-turns-websites-into-android-apps-5gan</link>
      <guid>https://dev.to/dron4e6h1u/i-built-an-open-source-tool-that-turns-websites-into-android-apps-5gan</guid>
      <description>&lt;h1&gt;
  
  
  I Built an Open-Source Tool That Turns Websites Into Android Apps
&lt;/h1&gt;

&lt;p&gt;Hey everyone!&lt;/p&gt;

&lt;p&gt;I’ve been working on a project called &lt;strong&gt;InteeBuild&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The idea is pretty simple:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;Give it a public website or HTML and get an Android project/APK/AAB without having to manually set everything up.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;GitHub:&lt;br&gt;
&lt;a href="https://github.com/Fluxionics/InteeBuild" rel="noopener noreferrer"&gt;https://github.com/Fluxionics/InteeBuild&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What can it do?
&lt;/h2&gt;

&lt;p&gt;InteeBuild currently supports things like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Website → Android app&lt;/li&gt;
&lt;li&gt;HTML → Android app&lt;/li&gt;
&lt;li&gt;APK / AAB builds&lt;/li&gt;
&lt;li&gt;Custom app name and package&lt;/li&gt;
&lt;li&gt;Custom icons&lt;/li&gt;
&lt;li&gt;Android permissions&lt;/li&gt;
&lt;li&gt;Background audio&lt;/li&gt;
&lt;li&gt;Native bridges&lt;/li&gt;
&lt;li&gt;GitHub Actions builds&lt;/li&gt;
&lt;li&gt;Build artifacts&lt;/li&gt;
&lt;li&gt;Build logs&lt;/li&gt;
&lt;li&gt;API access&lt;/li&gt;
&lt;li&gt;Webhooks&lt;/li&gt;
&lt;li&gt;APK inspection/decompilation&lt;/li&gt;
&lt;li&gt;Security checks for URLs and webhooks&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One of the parts I spent the most time on was the permission system.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;h2&gt;
  
  
  Security
&lt;/h2&gt;

&lt;p&gt;Since the server can receive URLs and APK files, I also added protections against things like:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;SSRF&lt;/li&gt;
&lt;li&gt;localhost/private IP access&lt;/li&gt;
&lt;li&gt;cloud metadata endpoints&lt;/li&gt;
&lt;li&gt;malicious ZIP/APK structures&lt;/li&gt;
&lt;li&gt;oversized inputs&lt;/li&gt;
&lt;li&gt;API abuse&lt;/li&gt;
&lt;li&gt;invalid webhooks&lt;/li&gt;
&lt;li&gt;rate-limit abuse&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There are also automated tests for many of these cases.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why did I make it?
&lt;/h2&gt;

&lt;p&gt;I wanted something that could take a website and make the Android side much less annoying.&lt;/p&gt;

&lt;p&gt;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.&lt;/p&gt;

&lt;p&gt;For example, adding a permission to Android's manifest doesn't magically make the website capable of using that hardware.&lt;/p&gt;

&lt;p&gt;So the project tries to distinguish between:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;declared → supported → generated → actually usable&lt;/code&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What's next?
&lt;/h2&gt;

&lt;p&gt;Right now I'm focusing more on stability and security instead of just adding more features.&lt;/p&gt;

&lt;p&gt;I want the core pipeline to be reliable:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;URL/HTML → Analyze → Configure → Audit → Build → APK/AAB&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;I'd love to hear feedback from other developers.&lt;/p&gt;

&lt;p&gt;GitHub:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/Fluxionics/InteeBuild" rel="noopener noreferrer"&gt;https://github.com/Fluxionics/InteeBuild&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;What would you improve or add to a tool like this?&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>android</category>
      <category>opensource</category>
      <category>webdev</category>
      <category>javascript</category>
    </item>
  </channel>
</rss>
