The changes that I typically add to these stubs are:Īdding declare(strict_types=1) to each file. This saves me a lot of time going through the stubs that I don't need to change. I tend to delete the stubs I know I will not use here and modify only the ones I know I will use. Now that my base Laravel application is set up for success, I can start publishing stubs that I commonly use and customize them to save me time during the development process. From here, I can start building exactly what I need. These packages set me up for building an API in a very friendly and easy-to-build way. Once I understand my data models, I start going through the dependencies I know I will need or want to use for this application. The Task Model will be relatively straightforward: I typically document these as YAML code blocks, as it allows me to describe the model in a friendly and easy way. Let's explore the data models that I need to create first. This includes:Ī general description of what I want to build.Ī rough design of the API endpoints I will need to create. The first step for me in every new application is to open the README file and start documenting what I want to achieve. Once this is in my IDE, I can start the work process. PHPStorm is my go-to IDE as it provides a robust set of tools for PHP development that help me with my workflow. Once this command has run and everything is set up and ready for me, I open this project in PHPStorm. However, feel free to use Inertia if you are more comfortable and want to follow along. If I am honest - this application's web functionality will be just for user management and API token creation. For this, I would typically choose Livewire, as I am most comfortable with it.

Laravel rapid application development