<?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: Alessandro Rasulo</title>
    <description>The latest articles on DEV Community by Alessandro Rasulo (@alex9978).</description>
    <link>https://dev.to/alex9978</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%2F2795773%2Fd9e48cfb-2450-4ecf-8f2f-db98a3b07c0b.jpg</url>
      <title>DEV Community: Alessandro Rasulo</title>
      <link>https://dev.to/alex9978</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alex9978"/>
    <language>en</language>
    <item>
      <title>How I Built FixerLab: A Simple Tool to Organize Repair Workflows</title>
      <dc:creator>Alessandro Rasulo</dc:creator>
      <pubDate>Sun, 03 May 2026 15:40:35 +0000</pubDate>
      <link>https://dev.to/alex9978/how-i-built-fixerlab-a-simple-tool-to-organize-repair-workflows-3koe</link>
      <guid>https://dev.to/alex9978/how-i-built-fixerlab-a-simple-tool-to-organize-repair-workflows-3koe</guid>
      <description>&lt;p&gt;Running a repair shop can get messy fast: scattered tickets, customers asking for updates, parts to order, overlapping deadlines.&lt;br&gt;&lt;br&gt;
As a developer and maker, I’ve been in that situation myself — and that’s why I built &lt;strong&gt;FixerLab&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;FixerLab is a web app designed for &lt;strong&gt;technicians, repair shops, and hobbyists&lt;/strong&gt; who want to keep their workflow organized without relying on spreadsheets, random chats, or overly complex enterprise software.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why I Built It
&lt;/h2&gt;

&lt;p&gt;After talking with several repair professionals (and experiencing the pain points firsthand), I realized there was no tool that was:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Simple&lt;/strong&gt; enough to use daily
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Fast&lt;/strong&gt; and mobile-friendly
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Designed around real repair workflows&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Clear&lt;/strong&gt; about the status of each job (Diagnosis, Waiting for Parts, Ready, Delivered…)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Most existing tools target large companies, not the people actually working at the repair bench.&lt;/p&gt;




&lt;h2&gt;
  
  
  What FixerLab Does
&lt;/h2&gt;

&lt;p&gt;Here are the core features:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Ticket management&lt;/strong&gt; with status, priority, and notes
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Parts tracking&lt;/strong&gt; for components and materials
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Repair history&lt;/strong&gt; by customer and device
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Clean dashboard&lt;/strong&gt; to highlight urgent jobs
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mobile support&lt;/strong&gt; for use directly in the workshop
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I’m actively adding new features based on user feedback.&lt;/p&gt;




&lt;h2&gt;
  
  
  Tech Stack
&lt;/h2&gt;

&lt;p&gt;FixerLab is built with:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;SvelteKit&lt;/strong&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Go + PostgreSQL&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;TailwindCSS&lt;/strong&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;I chose a modern but lightweight stack to keep development fast and scaling simple.&lt;/p&gt;




&lt;h2&gt;
  
  
  Want to Try It?
&lt;/h2&gt;

&lt;p&gt;FixerLab is live here:&lt;br&gt;&lt;br&gt;
&lt;strong&gt;&lt;a href="https://fixerlab.app" rel="noopener noreferrer"&gt;https://fixerlab.app&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If you work in a repair shop — or repair devices as a hobby — I’d love to hear your feedback.&lt;br&gt;&lt;br&gt;
I’m building FixerLab &lt;em&gt;together&lt;/em&gt; with the community of technicians.&lt;/p&gt;

</description>
      <category>productivity</category>
      <category>saas</category>
      <category>webdev</category>
    </item>
  </channel>
</rss>
