<?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[Asad's Dev Journal]]></title><description><![CDATA[Asad's Dev Journal]]></description><link>https://toolfrndhashnodedev.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 18 Nov 2026 13:57:23 GMT</lastBuildDate><atom:link href="https://toolfrndhashnodedev.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[What I Learned Building 30 Online Tools in One Week]]></title><description><![CDATA[What I Learned Building 30 Online Tools in One Week]]></description><link>https://toolfrndhashnodedev.hashnode.dev/what-i-learned-building-30-online-tools-in-one-week</link><guid isPermaLink="true">https://toolfrndhashnodedev.hashnode.dev/what-i-learned-building-30-online-tools-in-one-week</guid><category><![CDATA[webdev]]></category><category><![CDATA[JavaScript]]></category><category><![CDATA[sideproject]]></category><category><![CDATA[side project]]></category><category><![CDATA[#beginners #learningtocode #100daysofcode]]></category><category><![CDATA[Productivity]]></category><dc:creator><![CDATA[Asad Ilyas]]></dc:creator><pubDate>Fri, 13 Nov 2026 11:42:53 GMT</pubDate><content:encoded><![CDATA[<p>Seven days ago I had an idea: build a collection of free, no-nonsense online tools that run entirely in the browser. No signups, no uploads to strange servers, no ads blinking in your face while you try to calculate your BMI.</p>
<p>Today, <a href="https://toolfrnd.com">Toolfrnd.com</a> has 30 tools live and is getting real traffic from Google Search Console. Here's what I learned.</p>
<h2>The problem that started it all</h2>
<p>I was trying to convert a JPG to PDF for an application. Simple task, right?</p>
<p>The first result on Google asked me to create an account. The second added a watermark unless I paid $9.99/month. The third uploaded my personal document to a server in a country I'd never heard of.</p>
<p>I thought: "This should be a 20-line JavaScript file, not a $9.99/month SaaS."</p>
<p>That weekend, I started coding.</p>
<h2>The stack: boring on purpose</h2>
<p>Every tool on Toolfrnd uses the same stack:</p>
<ul>
<li><strong>HTML</strong> (one file per tool)</li>
<li><strong>Vanilla JavaScript</strong> (no React, no Vue, no bundler)</li>
<li><strong>CSS</strong> (one shared stylesheet)</li>
<li><strong>Cloudflare Pages</strong> (free hosting)</li>
</ul>
<p>No frameworks. No build step. No npm install. Just open the HTML file in a browser and it works.</p>
<p>Why? Because tools like a <a href="https://toolfrnd.com/tools/bmi-calculator">BMI calculator</a>, a <a href="https://toolfrnd.com/tools/password-generator">password generator</a>, or a <a href="https://toolfrnd.com/tools/base64-encoder">Base64 encoder</a> don't need a 300KB React runtime. They need 2KB of JavaScript that does one thing well.</p>
<h2>Lesson 1: Browser APIs are shockingly powerful</h2>
<p>When I started, I assumed I'd need backend code for things like:</p>
<ul>
<li>Generating QR codes</li>
<li>Creating PDFs</li>
<li>Hashing passwords (SHA-256, MD5)</li>
<li>Cryptographically secure random number generation</li>
</ul>
<p>Turns out, all of this is built into the browser:</p>
<ul>
<li><code>crypto.subtle</code> handles all cryptographic hashing</li>
<li><code>crypto.getRandomValues()</code> gives you secure random bytes</li>
<li><code>jsPDF</code> (one library, loaded from CDN) generates PDFs client-side</li>
<li><code>qrcode.js</code> makes QR codes in pure JavaScript</li>
</ul>
<p>I didn't need a server. Ever.</p>
<h2>Lesson 2: Privacy is a feature, not a feeling</h2>
<p>The biggest surprise? Users genuinely care about privacy.</p>
<p>When I added a line to my <a href="https://toolfrnd.com/tools/jwt-decoder">JWT decoder</a> that said "Your token is decoded in your browser. Nothing is sent to any server", engagement jumped.</p>
<p>People paste sensitive tokens into decoders all the time. The moment they know it's client-side, they trust the tool.</p>
<p>This applies to every tool. The <a href="https://toolfrnd.com/tools/password-generator">password generator</a> never transmits the generated password. The <a href="https://toolfrnd.com/tools/hash-generator">hash generator</a> processes your input locally. The <a href="https://toolfrnd.com/tools/jpg-to-pdf">JPG to PDF converter</a> never uploads your images.</p>
<p>You can verify this by disconnecting from the internet mid-conversion. Everything still works.</p>
<h2>Lesson 3: Boring SEO wins</h2>
<p>I spent zero dollars on marketing. All traffic came from:</p>
<ol>
<li>Writing good <code>&lt;title&gt;</code> and <code>&lt;meta description&gt;</code> tags</li>
<li>Using proper <a href="http://Schema.org">Schema.org</a> JSON-LD markup (<code>WebApplication</code> type)</li>
<li>Including a sitemap.xml and robots.txt</li>
<li>Adding breadcrumbs with structured data</li>
<li>Writing 800+ words of genuine content on each tool page</li>
</ol>
<p>By day 3, Google was indexing my pages. By day 5, I had 56 impressions and 3 clicks. By day 7, I had 139 concurrent real users at peak.</p>
<p>Nothing fancy. Just the SEO basics done consistently.</p>
<h2>Lesson 4: Ship ugly, polish later</h2>
<p>My first version of Toolfrnd looked terrible. Gray buttons, no icons, awkward spacing.</p>
<p>I shipped it anyway.</p>
<p>Then I iterated. Added a real logo. Fixed the color contrast (PageSpeed flagged it). Added favicons. Wrote an about page. Set up a contact form with Formspree.</p>
<p>The lesson: a shipped ugly tool beats a beautiful unshipped idea. You can always polish after people start using it.</p>
<h2>Lesson 5: Users want simple, not clever</h2>
<p>I built some "smart" features early on. A BMI calculator that compared your result to WHO data. A password generator with a complex entropy visualization.</p>
<p>Users ignored both.</p>
<p>What they wanted:</p>
<ul>
<li>Type number → See result</li>
<li>Click button → Get password</li>
</ul>
<p>That's it. No animations. No cleverness. Just input and output.</p>
<p>I removed the smart features. Engagement went up.</p>
<h2>The 5 tools that got the most love</h2>
<p>Based on real analytics from my first week:</p>
<ol>
<li><a href="https://toolfrnd.com/tools/bmi-calculator"><strong>BMI Calculator</strong></a> - Top search traffic from "bmi calculator" and "calculate bmi"</li>
<li><a href="https://toolfrnd.com/tools/jpg-to-pdf"><strong>JPG to PDF</strong></a> - People convert documents and screenshots daily</li>
<li><a href="https://toolfrnd.com/tools/password-generator"><strong>Password Generator</strong></a> - Developers love the crypto-secure option</li>
<li><a href="https://toolfrnd.com/tools/base64-encoder"><strong>Base64 Encoder/Decoder</strong></a> - Pure developer traffic</li>
<li><a href="https://toolfrnd.com/tools/qr-generator"><strong>QR Code Generator</strong></a> - Surprised me - mostly non-dev users</li>
</ol>
<h2>What I'd do differently</h2>
<p>If I started again, I'd:</p>
<ol>
<li><strong>Set up Google Search Console and Analytics on day 1</strong>, not day 3. I lost 2 days of data.</li>
<li><strong>Write the "About" and "Contact" pages first</strong>. EEAT (Experience, Expertise, Authoritativeness, Trustworthiness) matters for Google rankings.</li>
<li><strong>Build a design system first</strong>. I kept rewriting CSS for each tool before I extracted shared styles.</li>
<li><strong>Add</strong> <a href="http://Schema.org"><strong>Schema.org</strong></a> <strong>markup on day 1</strong>. Google's rich results eligibility is huge for click-through rate.</li>
</ol>
<h2>The honest numbers</h2>
<p>I don't want to make this sound bigger than it is. Here's the raw data after 7 days:</p>
<ul>
<li><strong>30 tools built</strong></li>
<li><strong>500+ unique visitors</strong></li>
<li><strong>139 concurrent users at peak</strong></li>
<li><strong>56 Google Search Console impressions</strong> (growing daily)</li>
<li><strong>3 Google Search clicks</strong> (page 2-3 rankings)</li>
<li><strong>$0 revenue</strong> (AdSense not applied yet, planning to apply in week 2-4)</li>
<li><strong>$12 spent</strong> (domain only - Cloudflare hosting is free)</li>
</ul>
<p>Not a startup success story. Just a small project that quietly works.</p>
<h2>Why I'm writing this</h2>
<p>Because 6 months ago I would have Googled "how to build a side project" and gotten 50 posts about Next.js, Supabase, Stripe integration, and complex architecture.</p>
<p>I want to tell beginners: you don't need any of that. You can ship 30 real tools with HTML, JavaScript, and a free Cloudflare Pages account.</p>
<p>The hardest part isn't the code. It's picking a problem small enough to solve in a day and shipping before you lose momentum.</p>
<p>If you want to try the tools, they're all live at <a href="https://toolfrnd.com">toolfrnd.com</a>. No signup, no tracking, no uploads. Just open and use.</p>
<p>I'll keep writing about what I learn as the project grows. Follow along if you're building your own side project.</p>
]]></content:encoded></item></channel></rss>