r/laravel • • Sep 23 '25

Package / Tool FilaForms - Native Filament form builder I built (visual builder, submissions, notifications, analytics)

439 Upvotes

After years of rebuilding contact forms, newsletter signups, and application forms for every single Laravel project, I finally snapped and built a proper solution.

FilaForms - A Filament plugin that handles ALL your public-facing forms in one go.

The Problem It Solves

Every Laravel app needs forms that visitors fill out. Contact forms, job applications, surveys, newsletter signups - we build these over and over. Each time writing validation, handling file uploads, setting up email notifications, building submission dashboards, adding CSV exports...

What I Built

A native Filament plugin that gives you:

  • Visual form builder with 25+ field types (including list-items, ratings, file uploads)

  • Drag & drop interface - no code needed for form creation

  • Submission management dashboard built into the Filament admin

  • Built-in analytics to see how your forms perform

  • Conditional logic & multi-step forms for complex workflows

  • Auto-responders & email/in-app notifications with customizable templates

  • CSV/Excel exports with bulk operations

  • Progress saving so users don't lose partially filled forms (coming soon)

The Technical Bits

  • It's pure Filament components under the hood (no iframes, no external JS libraries)

  • Self-hosted on your infrastructure - your data stays yours

  • Works with existing Filament panels and Livewire apps

  • Integrates with your current authorization

Some Background

I've been contributing to the Filament ecosystem for a while (you might know Relaticle CRM, FlowForge, or Custom Fields). This is solving a problem I've personally faced in every Laravel project.

Link: filaforms.app

Happy to answer any questions about the implementation, architecture decisions, or specific use cases. Also really interested in what types of forms you're all building most often - always looking for edge cases to handle better.


r/laravel • • Jan 24 '25

Package / Tool NativePHP finally goes truly native

373 Upvotes

r/laravel • • May 18 '26

Article One of my first ever PRs merged to Laravel Breeze! I have contributed to the framework I've been using for years, I'm so happy!

Post image
353 Upvotes

It's 4 lines if you count one empty line. Not to brag 😏

Link


r/laravel • • Apr 17 '25

Discussion Laravel: When you're the entire dev team and still ship faster

Post image
353 Upvotes

Saw this on LinkedIn, too relatable not to share.


r/laravel • • Aug 14 '26

Fully native Mac app with PHP, Laravel and Blade. No Electron, HTML/CSS/JS

Post image
336 Upvotes

This is what we've been building towards for almost 4 years: fully native UI, no PHP server, no Node. Just PHP embedded directly in a Swift shell, being executed immediately in response to button taps and other events, capable of re-rendering the UI at well over 240fps. From PHP & Laravel.

No HTML, no CSS, no JS, no Electron, no WebView.

And it can live directly alongside nativephp/mobile, which means we will have a single Laravel app that can render a fully functioning native app for iOS, Android, macOS, Windows and Linux from one codebase, just with a couple of Composer packages.

This is NativePHP Desktop v3 running SuperNative 🎉

Live demo on our livestream at 9am EST (roughly 12 hours from when I posted this)


r/laravel • • Jul 09 '25 This

Package / Tool Custom Fields v2.0 - Major Update for Filament Apps

335 Upvotes

Just shipped: Option Colors & Conditional Visibility 🎉

After months of development, I'm excited to share Custom Fields v2.0 - a significant update to our Filament package that lets you add dynamic custom fields without database migrations.

What's New in v2.0:

🌈 Option Colors

  • Add visual color coding to select fields and radio buttons

  • Perfect for status fields, priority levels, and categories

  • Clients love the visual clarity it brings to their data

👁️ Conditional Visibility

  • Show/hide fields based on other field values

  • Create smart, adaptive forms that respond to user input

  • No more cluttered forms - only show what's relevant

Why This Matters:

As Laravel developers, we've all been there - client wants "just a few custom fields" and suddenly you're writing migrations, updating models, creating form components, and spending days on what should be simple changes.

Custom Fields eliminates this pain entirely. Your clients can create their own fields through the admin panel, and when requirements change (they always do), you respond in minutes, not sprints.

Technical Highlights:

  • Zero database changes - Everything stored as JSON

  • Type safety - Full validation and casting support

  • Seamless integration - Works with existing Filament resources

  • Performance optimized - Efficient querying and caching

Field Types Supported:

Text, Number, Textarea, Rich Editor, Select, Multi-select, Radio, Checkbox, Date/DateTime, Color Picker, Tags, Toggle, Currency, Link, Markdown Editor, and more.

Real Developer Feedback:

"Cut our development time by 50% and our clients love being able to create exactly what they need without waiting for us to code it."

"I've tried building custom field functionality myself three times. This package does everything I needed and more, right out of the box."

Coming Soon:

Planning to open source this package - want to give back to the Laravel community that has given me so much.

Questions Welcome:

Happy to answer any technical questions about implementation, performance, or use cases. Always looking for feedback from fellow Laravel developers!

Stack: Laravel 12+, Filament 3+, PHP 8.2+

Live Demo: https://relaticle.com/

Documentation: https://custom-fields.relaticle.com/introduction

What do you think? Anyone else working on similar solutions for dynamic fields?


r/laravel • • Dec 08 '22

Discussion Taylor Otwell in his Work Station. Photo by his wife Abigail on Twitter.

Post image
318 Upvotes

r/laravel • • Sep 09 '20

Thoughts on some reactions to Jetstream here...

301 Upvotes

I thought I would share some thoughts regarding some user's reactions to Jetstream here on this board.

I've seen some criticism that Livewire / Inertia are "young" stacks that haven't been proven or are not used by enough people. Here is one flaw with that: the stack previously created by laravel/ui was used by even less people. It was not a properly configured Vue SPA. It was a weird mash-up of a single file Vue component with no Vue router and no reasonable way to even structure the application using Vue out of the box. It wasn't a good way to build an application. I never could have used it as configured to build a production ready application. It wasn't even setup to build an application at all without you manually reconfiguring everything to use Vue Router (or Inertia).

Regarding the "Livewire" stack in Jetstream. That is just Blade. You do not have to use Livewire at all. Livewire is not a sprawling UI framework that takes over your entire application. It is a tool for creating components that behave in a "Javascripty" way without using JavaScript. You can use it for a single portion of your site. It does not take over your application in the same way that something like Vue or React does. You can entirely ignore the "Livewire" part of that stack and just use Blade if you want to.

Inertia is just Vue without the complexity of Vue Router. I built Laravel Vapor as a Vue SPA and it's my personal opinion that working with Inertia is a *much more* productive way to pair the power of Vue with Laravel's backend routing system. Inertia is a small library that just gives you a way to render Vue components and hydrate their props from your Laravel backend. That's it. That's all it does.

Regarding Tailwind, it's just my opinion that it's a much better tool than Bootstrap. When I first started using it, I thought it was harder than Bootstrap. I was wrong. Bootstrap is harder than Tailwind. Bootstrap is less flexible and Bootstrap's approach to responsive feels like a pipe dream. Tailwind, in my opinion, is just a more robust and powerful way to build application UIs.

Regarding React / Bootstrap users being "screwed". You aren't. Anyone can build an open source package that is a scaffold for Laravel + React + Bootstrap applications and release it on GitHub. The previous laravel/ui package works fine with Laravel 8.x for applications that are upgrading. For those with namespace problems - just add the $namespace property back into your RouteServiceProvider.

Finally, thank you all for using Laravel. I really appreciate it and I have a blast developing it and trying to make it as good as I can for everyone. Jetstream is simply my vision for what a great, productive starting point for Laravel looks like in 2020. Different people may have a different vision. They are free to code theirs and release it.


r/laravel • • Sep 06 '21

Did you know you can use a shorter syntax for many ‚use‘ statements?

Post image
297 Upvotes

r/laravel • • Jul 13 '20

News Vemto - Upcoming Laravel Code Generator and Studio

290 Upvotes

r/laravel • • Sep 01 '19

When you want to hire Taylor Otwell for your laravel project as an intern

Post image
288 Upvotes

r/laravel • • Sep 03 '26

Taylor Otwell disabled GitHub issues on most Laravel open-source packages repositories

275 Upvotes

This would be ok if it wasn't that Taylor is known for closing PRs without any explanation or feedback (only the stock message he always use), so you often don't know what's wrong with your PR. It happened me twice already and it's totally demotivating.

Tweet: https://x.com/taylorotwell/status/2095516796748996843


r/laravel • • May 08 '25

Discussion I hate to admit this, but Laravel Cloud is nowhere near production-ready

274 Upvotes

I moved my app from DigitalOcean droplet(6$) to Laravel Cloud (~80$), a couple of weeks after it was released, and I hate to admit this but I wish I didn’t do that. I was ready to pay more money, thinking that I won’t have to care about downtimes anymore, but it’s actually the opposite.

  • Random outages, sometimes up to 20 minutes

  • Support replying 24 hours later, no matter the urgency of the issue

  • Requests avg. spiking from 200ms to 20 seconds for periods of hours

Don’t get me wrong, Laravel team is awesome, and their products are top-tier, but I wish they’d admit that Cloud is just not prod-ready yet, so developers can make informed choices.


r/laravel • • Feb 28 '25

News Non-Volt Livewire starter kit now available

270 Upvotes

Hey all - dropped a non-Volt flavor of the Livewire starter kit for you.

https://x.com/taylorotwell/status/1895584390580957337


r/laravel • • Feb 24 '25

Discussion New Laravel website. First impressions.

262 Upvotes

First impression ? Bad.
After re-evaluation? Fu*king horrible.

Hijacked scroll, you need to scroll 5 times to move out of a section.
Page down to navigate? Good luck, you will "miss" information that's only visible after you "scroll" a specific section of the page.

Mobile ? I am not even going to start here.

Disc: This is my opinion and does not reflect the opinion of any of my peers.


r/laravel • • Oct 03 '20

Jetstream is completely bloated mess

262 Upvotes

I want to share my first experiences with Jestream and Fortify in Laravel 8. I decided to give it a shot yesterday and all I can say is that I definitely will try to avoid the new scaffolding in future projects. Maybe doing my own scaffolding when I have some time.

From my point of view auth scaffolding was one of the best features in Laravel for a long time. It gave you a perfect (minimal) starting point for your application without trying to guide you in some specific direction or taking too much work off you. You just typed php artisan make:auth and you were good to go. This functionality gave you some perfectly working default controllers you could utilize with whatever type of frontend stack you wanted. You could build your frontend with plain blade templates in HTML, you could utilize Livewire components, you could even adapt a SPA to the existing endpoints. There was an Auth::routes() in your routes/web.php and it was clear where those routes come from and which endpoint they were hitting. Wanted to add or alter some behavior? No problem - just go to your auth controllers and override whatever method you wanted to override.

When I used Jetstream for the first time, I decided to give Livewire a shot because I felt like this would be the least kind of "intruding" scaffolding. Turns out you can now decide between pest and cholera. Even given the fact I'm using Livewire and Tailwind on a daily base, I had huge trouble starting a blank application from scratch. The provided auth scaffolding views were entirely built from custom components. I needed to look up where I could edit those components and came to the conclusion that I was required to publish the Jetstream assets. My IDE greeted me with a full monitor height of uncommitted files I could now edit to match the design of the components to my regular application layout and design.

Next on I wanted to look into the new login/register/password logic and looked for the controllers. Turns out they are gone. No more controllers. All the logic for authentication which is basically just worth some hundred lines of code are completely over-abstracted and hidden in some huge pile of interfaces, contracts and closures that I were required to dissect in order to understand how it's working under the hood.

Another problem I encountered were the huge load of features that are enabled by default. Some features or functionality you can enable in the Providers, other ones just in some configuration files. Everything is splattered in some other location. Though you were done taming Jetstream - well let me sing you the song of Fortify. Took me another 10 minutes figuring out how to add a simple array of data to the register view. Turns out you need to put some override-closure-method in your FortifyProvider.

I'm neither new to Laravel nor unfamiliar with Tailwind, Livewire or the framework core itself. But in comparison to what I was used to from Laravel 7 the new scaffolding with Jetstream in Laravel 8 is a completely bloated mess. Profile photo functionality enabled by default? Really? Please remove this stuff from the framework and stuff it in some 99$ package; that's what the Laravel community is used to. Whenever there were PRs in the past that added "too much functionality" to the framework were Taylor thought not everyone would profit from it, it got declined. Now it doesn't get into my head how some simple stuff like authentication, e-mail verification and password reset functionality could get that bloated and I'm really not eager to see what future may bring.


r/laravel • • Dec 28 '20

News Some love for Taylor

257 Upvotes

Hi Taylor, You’ll probably never get this, but if you do, read carefully: As someone who started their professional career as a Laravel developer and then had to switch to Drupal (only due to Corona), I’m forever grateful for you and the masterpiece you created called Laravel and all the subsequent services whether paid or not. I truly never felt losing something so precious such as the ability to write Laravel apps for living, especially when alternative was Drupal. I feel like I time traveled back to the 90s just for the fact that you need raw sql to query the database, or the fact there is no tinker console. Please don’t stop doing what you do best which is to set trends in software development, and continue your amazing work with Laravel transition to SPA. I truly can’t wait to get back to developing Laravel applications full time.

#############

Update: I have returned to to building laravel full time. Thanks all


r/laravel • • Oct 08 '24

Tutorial Look Mom I finally did it! Laravel API Course with 24 videos, for free. Aimed at developers wanting to up their API game.

Thumbnail
juststeveking.link
256 Upvotes

r/laravel • • Nov 24 '24 Heart of Silver

Article Over 290 Laravel/PHP tips I've collected so far 🙌

Thumbnail
github.com
252 Upvotes

r/laravel • • Jul 09 '23

Discussion Dear PHPStorm. It's Illuminate\Http\Request. It's *always* Illuminate\Http\Request.

Post image
249 Upvotes

r/laravel • • Jul 30 '25

Package / Tool The Laravel Idea Plugin is Now Free for PhpStorm Users | The PhpStorm Blog

Thumbnail
blog.jetbrains.com
248 Upvotes

r/laravel • • Sep 23 '25 Helpful

News Vemto 2 now is Open-Source under MIT license

243 Upvotes

Hi everyone!

I'm delighted to announce that Vemto is now a fully open-source project, published under the MIT license.

A few months ago, I wrote a blog post explaining in detail why Vemto would become open-source.

At the time, I wasn't sure which license to use, but after talking to countless users and customers, I ended up opting for the MIT license.

It took me a while to prepare this repository, for personal reasons, but I finally managed to increase the number of tests to over 400, covering at least the most critical parts of the application, and I will continue adding more tests overtime.

I also managed to finish writing much of the internal development documentation.

I hope you enjoy it, and if you have any questions, please email me at [email protected].

By Tiago Rodrigues


r/laravel • • Nov 25 '25

Package / Tool FilaForms — public form builder plugin for FilamentPHP [Black Friday: 30% off]

242 Upvotes

I got tired of rebuilding form infrastructure on every project.

Contact forms, feedback forms, surveys — each time writing migrations, validation, submission handling, notifications...

So I built FilaForms: a Filament plugin with a visual form builder, submission tracking, and analytics.

One-time purchase. Self-hosted. No subscriptions.

**30% off through Monday for Black Friday.**

Here's a quick demo. Happy to answer questions.

https://filaforms.app


r/laravel • • Feb 18 '26 Bravo

Package / Tool I built this Laravel playground that runs completely in your browser (with no backend)

240 Upvotes

Hey everyone, it's me, Andrew.

I spent the last week or so tinkering around with what I've called Liminal. It's a static, 100% free and open source, Laravel playground that runs entirely on the client-side. It's built using Vue, TypeScript, Vite, and php-wasm (WebAssembly).

It's got:

  • A full code editor

  • SQLite db

  • Artisan commands

  • GitHub imports

  • Project exports

  • Sharable URLs

  • Two-way file syncing to your local desktop

And some more small features planned!

You can check out the live version at liminal.aschmelyun.com where it's hosted with Cloudflare pages, or you can run it yourself by following the instructions on the GitHub repo readme.

If this seems useful to you, or you have any suggestions for what could be done to make it more useful, let me know here or by creating an issue on GitHub! It's still a WIP, but I'm excited to show it off.