<?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: Mobterest Studio</title>
    <description>The latest articles on DEV Community by Mobterest Studio (@mobterest_studio).</description>
    <link>https://dev.to/mobterest_studio</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%2F3878462%2Fd2ce0f2e-8397-4c5a-b31e-84012b16395e.png</url>
      <title>DEV Community: Mobterest Studio</title>
      <link>https://dev.to/mobterest_studio</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/mobterest_studio"/>
    <language>en</language>
    <item>
      <title>Dartform: A Visual IDE Companion for Serverpod Developers</title>
      <dc:creator>Mobterest Studio</dc:creator>
      <pubDate>Tue, 14 Apr 2026 12:30:23 +0000</pubDate>
      <link>https://dev.to/mobterest_studio/dartform-a-visual-ide-companion-for-serverpod-developers-3f7b</link>
      <guid>https://dev.to/mobterest_studio/dartform-a-visual-ide-companion-for-serverpod-developers-3f7b</guid>
      <description>&lt;p&gt;If you’ve been watching the Dart backend ecosystem, you’ve probably come across Serverpod.&lt;/p&gt;

&lt;p&gt;Type-safe endpoints. Code generation. A Dart-native ORM. Auth. Real-time. Built specifically to pair with Flutter. The Serverpod team has shipped something that makes building a full-stack Dart application genuinely possible and they’ve done it with a level of care that shows in every release.&lt;/p&gt;

&lt;p&gt;I’ve been building with it in production. And the experience of working with the core has been good. But the longer I used it, the more clearly I could see one gap.&lt;/p&gt;

&lt;h2&gt;
  
  
  The gap: no visual layer for designing your backend
&lt;/h2&gt;

&lt;p&gt;Serverpod developers currently have no visual way to design and architect their backend.&lt;/p&gt;

&lt;p&gt;Every schema change means running the generator and then re-reading the output to reorient because there’s no diagram that updates automatically. Every endpoint test means writing curl or maintaining a Postman collection in parallel. Every time you want to understand your architecture, you open files.&lt;/p&gt;

&lt;p&gt;Compare this to the Flutter app side: Flutter DevTools gives you a widget inspector, a performance overlay, a network monitor. The app is legible. You can see it. You can reason about it visually.&lt;/p&gt;

&lt;p&gt;The Serverpod backend doesn’t have that yet. It’s not a criticism; it’s just where a growing framework is in its journey. The core is exceptional. The visual tooling layer is still being built.&lt;/p&gt;

&lt;p&gt;I wanted to help build it.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I built: Dartform
&lt;/h2&gt;

&lt;p&gt;Dartform is a visual IDE companion for Serverpod developers. It gives you the ability to design, architect, and navigate your Dart backend visually without digging through generated code to understand what you built.&lt;/p&gt;

&lt;p&gt;It’s a native macOS application. It reads your existing Serverpod project; no configuration, no backend changes, no new dependencies and gives you:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;An auto-generated ER diagram built from your schema files. Every model, every relationship, every field type rendered as a navigable diagram that updates as your schema evolves. Your backend architecture, visible at a glance.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;An endpoint browser with request testing built in. Browse all your Serverpod endpoints in one view. Test requests without leaving the tool; no Postman, no curl scripts, no external collection to maintain.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;A model and relationship viewer. Navigate your backend the way you navigate your Flutter app by looking at it, not by reading files about it.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What Dartform isn’t
&lt;/h2&gt;

&lt;p&gt;Dartform isn't here to compete with Serverpod, it's built to complement it. Think of it as a productivity layer that sits on top of your backend workflow, making the day-to-day faster and more visual. Serverpod is the first integration, but the vision is broader; more Dart backend solutions are coming.&lt;/p&gt;

&lt;h2&gt;
  
  
  Who it’s for
&lt;/h2&gt;

&lt;p&gt;Dartform is built for Flutter developers who run Serverpod in production on macOS currently, and who have felt the absence of visual tooling without quite having a name for it.&lt;/p&gt;

&lt;p&gt;If you’ve ever re-read generated files to understand a schema you designed yourself, Dartform is for you.&lt;/p&gt;

&lt;h2&gt;
  
  
  A note on the ecosystem
&lt;/h2&gt;

&lt;p&gt;To the Serverpod team, thank you for building something worth building around. Dartform exists because your framework does. Keep going.&lt;/p&gt;

&lt;p&gt;Serverpod deserves a rich visual tooling ecosystem. This article, and this tool, are my contribution to building one.&lt;/p&gt;

&lt;p&gt;Dartform is available now at &lt;a href="https://dartform.dev/" rel="noopener noreferrer"&gt;dartform.dev&lt;/a&gt;, distributed as a desktop tool.&lt;/p&gt;

&lt;p&gt;Feature requests and feedback live at &lt;a href="https://dartform.dev/#community" rel="noopener noreferrer"&gt;https://dartform.dev/#community&lt;/a&gt;  . If you’re using Serverpod, I’d genuinely love to hear what’s still missing.&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>dart</category>
      <category>serverpod</category>
      <category>tooling</category>
    </item>
  </channel>
</rss>
