<?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: Rao Imtinan</title>
    <description>The latest articles on DEV Community by Rao Imtinan (@imtinandev).</description>
    <link>https://dev.to/imtinandev</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%2F4115881%2F744a23a1-06c5-4860-af42-881f9e31bf38.png</url>
      <title>DEV Community: Rao Imtinan</title>
      <link>https://dev.to/imtinandev</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/imtinandev"/>
    <language>en</language>
    <item>
      <title>Why I Built Nazamos: A 100% Client-Side, Zero-Logging Developer Suite</title>
      <dc:creator>Rao Imtinan</dc:creator>
      <pubDate>Tue, 08 Sep 2026 14:00:47 +0000</pubDate>
      <link>https://dev.to/imtinandev/why-i-built-nazamos-a-100-client-side-zero-logging-developer-suite-3gfe</link>
      <guid>https://dev.to/imtinandev/why-i-built-nazamos-a-100-client-side-zero-logging-developer-suite-3gfe</guid>
      <description>&lt;h3&gt;
  
  
  🚀 The Problem
&lt;/h3&gt;

&lt;p&gt;A few weeks ago, while debugging an API response containing sensitive customer metadata and session tokens, I needed a quick JSON formatter. I clicked the top Google result, but before pasting my payload, I paused and opened the Chrome DevTools Network tab. &lt;/p&gt;

&lt;p&gt;To my surprise, most popular online formatters:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;Leak Data:&lt;/strong&gt; They send your payload via a POST request to their backend server just to run a standard parser.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Are Bloated:&lt;/strong&gt; The pages are packed with heavy display ads and tracking cookies.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Have Poor Performance:&lt;/strong&gt; Noticeable input lag on files over 2MB.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I wanted something clean, modern, and mathematically private. That’s why I built &lt;strong&gt;&lt;a href="https://nazamos.com" rel="noopener noreferrer"&gt;Nazamos&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;




&lt;h3&gt;
  
  
  🔥 What Makes It Different?
&lt;/h3&gt;

&lt;p&gt;There are dozens of formatters online, but Nazamos is built strictly around three core requirements:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. 🔒 Zero Network Egress on Payloads&lt;/strong&gt;&lt;br&gt;
If you inspect the Network tab on Nazamos, you will see zero outgoing API calls when you paste, parse, or convert data. Every single operation runs entirely inside your browser's V8 runtime. Once the static assets load, you can literally disconnect your Wi-Fi and the entire suite continues to operate without breaking.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. ⚡ Workflow-Centric (Not Just a Prettifier)&lt;/strong&gt;&lt;br&gt;
Formatting is only the first step. In real-world full-stack development, you need actionable data:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;  &lt;strong&gt;TypeScript &amp;amp; Zod Generation:&lt;/strong&gt; Paste a payload and instantly produce ready-to-use interfaces and runtime schemas (&lt;a href="https://nazamos.com/json-to-typescript" rel="noopener noreferrer"&gt;JSON to TypeScript&lt;/a&gt; / &lt;a href="https://nazamos.com/json-to-zod" rel="noopener noreferrer"&gt;JSON to Zod&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Collapsible Tree Inspection:&lt;/strong&gt; Search specific keys, collapse deep nodes, and copy exact path references easily with the &lt;a href="https://nazamos.com/json-tree-viewer" rel="noopener noreferrer"&gt;JSON Tree Viewer&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Bi-directional XML Handling:&lt;/strong&gt; Instant indentation and two-way JSON/XML conversions without needing command-line tools like &lt;code&gt;xmllint&lt;/code&gt; (&lt;a href="https://nazamos.com/xml-formatter" rel="noopener noreferrer"&gt;XML Formatter&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;  &lt;strong&gt;Side-by-Side Diffing:&lt;/strong&gt; Highlight additions, deletions, and schema mutations between two API responses (&lt;a href="https://nazamos.com/json-diff" rel="noopener noreferrer"&gt;JSON Diff&lt;/a&gt;).&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;3. 🌑 Zero Ad Clutter &amp;amp; Low Latency&lt;/strong&gt;&lt;br&gt;
No flashing banners. No tracking pixels. Just a native dark-mode interface that feels like an extension of your IDE, engineered to handle massive payloads smoothly without freezing the UI thread.&lt;/p&gt;




&lt;h3&gt;
  
  
  🛠️ The Tech Stack
&lt;/h3&gt;

&lt;p&gt;Built with &lt;strong&gt;Next.js 14&lt;/strong&gt;, &lt;strong&gt;TypeScript&lt;/strong&gt;, and &lt;strong&gt;Tailwind CSS&lt;/strong&gt;. The primary technical challenge was isolating client-side DOM parsing and optimizing state transitions to keep the editor highly responsive on large datasets.&lt;/p&gt;




&lt;h3&gt;
  
  
  💬 Looking for Community Feedback
&lt;/h3&gt;

&lt;p&gt;Nazamos is live and 100% free to use at &lt;strong&gt;&lt;a href="https://nazamos.com" rel="noopener noreferrer"&gt;nazamos.com&lt;/a&gt;&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;I'm actively refining this toolset for developers. If you work with JSON, XML, or schema migrations daily, what utility or converter do you find yourself missing most in your daily workflow? &lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>programming</category>
      <category>devex</category>
    </item>
  </channel>
</rss>
