Developer experience
With several essential backend features built, we can now focus on the developer experience aspects. Earlier referenced in Figure 7.1, this is the second important aspect of the framework we will focus on. The goal behind introducing framework-adjacent developer tools is to lessen the friction of adapting the features of our framework. It also helps to streamline the experience and create a unified way to work with the framework’s primitives.
To enable most of this experience, we will rely on the componium executable that ships with the framework when it is installed. This executable will take care of a lot of mundane tasks, such as initializing applications and scaffolding standard components. It will also eliminate common points of friction by enabling features such as live server reload.
In the next three subsections, we will explore three potential developer experience offerings that you can provide to the users of your framework.
