<?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: Samarth</title>
    <description>The latest articles on DEV Community by Samarth (@samarth_12).</description>
    <link>https://dev.to/samarth_12</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.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3891142%2Fe8ad6d91-8b22-4946-9a97-cbd715a59413.png</url>
      <title>DEV Community: Samarth</title>
      <link>https://dev.to/samarth_12</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/samarth_12"/>
    <language>en</language>
    <item>
      <title>I built a free PDF toolkit for internet cafés — need honest feedback</title>
      <dc:creator>Samarth</dc:creator>
      <pubDate>Thu, 23 Apr 2026 09:32:36 +0000</pubDate>
      <link>https://dev.to/samarth_12/i-built-a-free-pdf-toolkit-for-internet-cafes-need-honest-feedback-1kaf</link>
      <guid>https://dev.to/samarth_12/i-built-a-free-pdf-toolkit-for-internet-cafes-need-honest-feedback-1kaf</guid>
      <description>&lt;p&gt;Internet cafés handle a surprising amount of PDF work every day — merging documents, splitting files, converting formats, etc.&lt;/p&gt;

&lt;p&gt;Most tools out there are either:&lt;/p&gt;

&lt;p&gt;Paid&lt;br&gt;
Too complex&lt;br&gt;
Or not optimized for quick daily use&lt;/p&gt;

&lt;p&gt;So I built a simple tool to solve this:&lt;br&gt;
👉 &lt;a href="https://pro-pdf-toolkit.onrender.com/" rel="noopener noreferrer"&gt;https://pro-pdf-toolkit.onrender.com/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;What it does:&lt;/p&gt;

&lt;p&gt;Merge PDFs&lt;br&gt;
Split PDFs&lt;br&gt;
Convert files&lt;br&gt;
Basic PDF utilities&lt;/p&gt;

&lt;p&gt;Goal:&lt;br&gt;
Keep it fast, simple, and actually useful for real café workflows.&lt;/p&gt;

&lt;p&gt;I’m not here to promote it — I genuinely want feedback from people who might use something like this.&lt;/p&gt;

&lt;p&gt;If you get a chance to try it, I’d love to know:&lt;/p&gt;

&lt;p&gt;Does it actually help in real usage?&lt;br&gt;
What feels missing or slow?&lt;br&gt;
What would make it 10x better?&lt;/p&gt;

&lt;p&gt;Your input will directly influence what I build next 🚀&lt;/p&gt;

</description>
      <category>news</category>
      <category>learning</category>
      <category>marketing</category>
      <category>tooling</category>
    </item>
    <item>
      <title>🚀 Devs, would you actually use this?</title>
      <dc:creator>Samarth</dc:creator>
      <pubDate>Wed, 22 Apr 2026 16:07:26 +0000</pubDate>
      <link>https://dev.to/samarth_12/devs-would-you-actually-use-this-3fc2</link>
      <guid>https://dev.to/samarth_12/devs-would-you-actually-use-this-3fc2</guid>
      <description>&lt;p&gt;We’re building a tool and need honest feedback 👇&lt;br&gt;
💡 The Idea&lt;br&gt;
Paste your website URL → get a complete performance breakdown:&lt;br&gt;
⚡ Strengths (what you're doing right)&lt;br&gt;
🐢 Weaknesses (what’s slowing you down)&lt;br&gt;
🎯 Exact causes of performance issues&lt;br&gt;
🛠️ Suggested fixes with code&lt;br&gt;
🔥 Extra Features&lt;br&gt;
🔍 Compare Mode → Your site vs competitor&lt;br&gt;
🤖 Auto Suggestions → Where &amp;amp; what to improve&lt;br&gt;
😈 Roast Mode → Brutally honest website feedback (for fun + insights)&lt;br&gt;
❓ The Real Question&lt;/p&gt;

&lt;p&gt;Would this actually help you as a developer?&lt;br&gt;
Would you use something like this regularly?&lt;br&gt;
What would make it 10x more useful?&lt;br&gt;
Is “roast mode” useful or just gimmick?&lt;/p&gt;

&lt;p&gt;🎯 Goal&lt;br&gt;
We’re not building another generic audit tool.&lt;br&gt;
We want something practical, dev-focused, and actually actionable.&lt;/p&gt;

&lt;p&gt;Be brutally honest 👇&lt;br&gt;
Your feedback will shape what we build.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>productivity</category>
      <category>nextjs</category>
      <category>startup</category>
    </item>
    <item>
      <title>LumosUI: Reducing Repetitive UI Work in Next.js Apps</title>
      <dc:creator>Samarth</dc:creator>
      <pubDate>Tue, 21 Apr 2026 18:18:55 +0000</pubDate>
      <link>https://dev.to/samarth_12/lumosui-reducing-repetitive-ui-work-in-nextjs-apps-29li</link>
      <guid>https://dev.to/samarth_12/lumosui-reducing-repetitive-ui-work-in-nextjs-apps-29li</guid>
      <description>&lt;p&gt;I built LumosUI out of frustration with the repetitive UI setup on every new project.&lt;/p&gt;

&lt;p&gt;The library is built on Next.js + Framer Motion + Tailwind and includes ~20 advanced components (bento grids, spotlight cards, animated heroes, scroll-reveal primitives, magnetic interactions). Components are structured to be copied into existing projects without requiring LumosUI as an installed dependency.&lt;/p&gt;

&lt;p&gt;The interesting part is the prompt system. The library ships with structured Claude AI prompts and skills designed to help developers scaffold landing pages and full frontends from a product description. The prompts are component-aware — they reference LumosUI components by name and generate layouts that map to the actual component API.&lt;/p&gt;

&lt;p&gt;Technical stack: Next.js 14 App Router, Framer Motion 11, Tailwind CSS 3, TypeScript.&lt;/p&gt;

&lt;p&gt;It's launching as a paid lifetime-access product ($25 for early users). I know some will object to paid developer tooling, so here's my reasoning: I want to keep it a focused, maintained library rather than an open-source project that gets 3 PRs and dies. Early adopters get all future components automatically.&lt;/p&gt;

&lt;p&gt;Live demo and waitlist: &lt;a href="https://www.lumosui.site/" rel="noopener noreferrer"&gt;https://www.lumosui.site/&lt;/a&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>react</category>
      <category>nextjs</category>
      <category>frontend</category>
    </item>
  </channel>
</rss>
