Summary

This explores the idea of improving the developer experience (DX) for Serverpod by evolving Serverpod Insights into a more comprehensive developer platform. The goal is to reduce setup friction, prevent common configuration errors, and streamline repetitive workflows without changing Serverpod’s core architecture.

Motivation

Serverpod already provides a strong experience for Flutter developers by enabling development within a single tech stack across the entire mobile engineering lifecycle. However, there are still areas where developers face friction during setup, configuration, and repetitive code generation. Improving DX in these areas can help developers move from project creation to productive development more quickly and with fewer errors.

Goals

• Reduce cognitive overhead during project setup and configuration
• Minimize common mistakes in database and model definition
• Automate repetitive workflows without hiding core Serverpod concepts
• Build on existing tools rather than introducing unnecessary fragmentation

Non-Goals

• Replacing the Serverpod CLI
• Abstracting away Serverpod internals to the point where developers lose control
• Introducing breaking changes to existing Serverpod projects

Proposed Direction

Instead of introducing a new standalone tool, this RFC proposes exploring an evolution of Serverpod Insights into a broader developer experience platform. Since Insights is already clean, reliable, and focused, it could act as a foundation for guided workflows and automation.

To better communicate the idea, I also put together a quick visual concept that illustrates the overall direction and workflow:
https://youtu.be/gdmELt9eVC8

Potential Features

Command Execution via UI

Core Serverpod CLI commands are run automatically after certain steps are made:

• Project creation
• Code generation
• Common development workflows

Guided Database & Model Design

• Visual interface for defining models
• Automatic generation of YAML files
• Built-in validation to prevent common issues such as:
  • Incorrect indentation
  • Invalid or unsupported data types

Boilerplate Code Generation

• Optional auto-generation of CRUD operations for selected models
• Particularly useful for large or data-heavy projects

Expected Benefits

• Faster onboarding for new Serverpod developers
• Fewer configuration-related errors
• Reduced time spent on repetitive setup tasks
• Improved productivity in larger codebases
• Access to the database designed without depending on external platforms such as Postico (which not everyone can access)

Open Questions

• Does evolving Serverpod Insights align with the long-term direction of the ecosystem?
• Which workflows would benefit most from UI-driven automation?
• What level of abstraction feels helpful without becoming restrictive?

Feedback Requested

Community feedback is requested on the overall direction, scope, and feasibility of this idea, as well as suggestions for workflows that would benefit most from improved tooling.