The first thing that we'll wanna look at is the native PHP documentation, So head to native PHP dot com and we can start here. Go to docs, and you'll see straight away that we're on the mobile documentation, and we can switch between mobile and desktop documentation easily here. This switcher is always available on every page. The other thing to note is that there's a search right here, which you can always get to by pressing command K,

The other thing to note is that there's a search right here, which you can always get to by pressing command K, and we can search the documentation for topics that we might be interested in. The other thing in workflow that we need to cover is how different it's gonna be to what you're used to when you're just building web applications with Laravel. So think about how you normally will do your work. You probably open your project and your favorite IDE or editor.

You probably open your project and your favorite IDE or editor. You'll go into the code files and you'll make some changes, and then you hit save, and then you'll maybe jump over to a browser and you'll hit refresh. The feedback cycle of development is so rapid. It's what makes PHP a real joy to work with. There's no compilation step, there's no waiting around for your application to be ready.

There's no compilation step, there's no waiting around for your application to be ready. You can go straight from editing a file to seeing the change in the browser within moments. Now, we've worked really hard with native PHP to make it feel the same way, but the reality is that there are some steps in between to get there, which make it not quite exactly like that, and that means that it is a different workflow. You're going to have to run some commands

and that means that it is a different workflow. You're going to have to run some commands before you make some changes in order to see them immediately in the environments that you are working in. Also, in some cases, it's not even possible to have the change be made and then immediately reflected on the other side. What I find useful is to still build my applications very much in this the way

What I find useful is to still build my applications very much in this the way that I'm used to, which is in the browser, and because they're just Laravel applications for the most part, that's fine. When you're focusing on building core functionality and ui, then using the browser can generally be okay, but it does fall down when you need to access native features because you can't access

to access native features because you can't access those tools from within the browser. We have to be running in the environment of the application that we're building in order to tap into its native features. Take some time to get used to operating in this slightly new way where you're having to run a process that's maybe watching your files and then seeing changes happen somewhere else other

run a process that's maybe watching your files and then seeing changes happen somewhere else other than the web browser. But there's just a little bit more that we need to go through before we can get there. Let's talk about databases for a minute.