Mvp using nova

Nova is very useful for an MVP because of the speed! It's so easy to show statistics and everything from your models. Writing everything from scratch takes a long time as well. Just start coding away with Nova. If Nova doesn't suit you can always build something new around it to manage the application :)

Another good point about using Nova is that if another team or company is going to work on the project they probably already know Nova because it's the default admin panel.

While I agree with @bobbybouwmann, I wouldn't use Nova in production. I personally hated the Nova experience because I feel like Nova itself is a MVP. It's extremely rigid, lacks a lot of basic CMS features and still has a lot of bugs. In addition, the two things that irritated me the most was the UX (way too many clicks and doubtful UX decisions in general), as well as the support behind Nova. I've seen multiple highly pertinent requests get shut down in a pretty harsh way with a pathetic reply.

I've not yet used other Laravel CMS options, but I know that some people moved from Nova to October CMS and enjoyed their experience.

@piljac1 I don't have any issues with Nova. We're running it for multiple applications in production. I do have to agree that the UX can be a bit better and that also the number of requests that are done on the background can be more efficient.

@bobbybouwmann It's a time saver for sure and is pretty stable if you're not using in dept features. It can be a good choice for customers with limited budgets, but for bigger budget customers with specific needs, I wouldn't recommend it.