Taylor discusses Jetstream and Laravel UI

Yea i saw that on Reddit. people these days 🤷‍♂️ miscommunication between Laravel infatuated fans and the general public who are not interested in Livewire/inertia with that utility first CSS framework

Would be great to have a text transcription for no english people (like me) that can't understand vocal version !

@bestmomo Basically

• Laravel UI will be maintained
• On twitter sounded like people wanted livewire and the jetstream stuff
• But many on other hand don't want.

I am just glad UI will be maintained, he said through laravel 9, 10, etc.

I like UI better than Fortify.

And @bestmomo I hope you are doing fine.

@jlrdw

I'm great thanks, hope you are too ;)

Thank you for the fast review. I like Fortify, it's really easy to use with custom views.

@bestmomo do you mean just fortify or scaffold with jetstream?

@jlrdw

I mean Fortify, without Jetstream, and with custom views.

I will have to try that also because I do not use inertia or Livewire. Thanks.

Also in another post @snappy referenced this YouTube series, I am going to watch it later it's on fortify:

https://www.youtube.com/playlist?list=PLxFwlLOncxFIbxi2gQCN3SR5e3-WB-4T2

Laravel UI doesn't require to watch any series :P Just install and code speak for itself.

It take me a whole week to create UI for Fortify, too many abstractions in my opinion. A bit frustrating for build something on top of it.

It's good if you need to handle multiple frontend like jetstream is doing, but if you have just one frontend as all of us then Laravel UI it's more simple and elegant starting point.

I am glad to hear from Taylor that he will continue to keep Laravel UI in future version, unfortunately for me I make already the UI for Fortify.

@thewebartisan7 if you do a new project with just laravel ui, you could:

• copy current to a folder, laravelold exclude vendor folder
• if in windows, use a tool called winmerge to compare.

Then just copy your custom models, views, controllers over.

Linux should have similar compare tools.

In fact when I upgraded to 8 from 7, that's what I did, (reverse upgraded). Made new project, and brought over custom stuff, as I also have service folder, custom helpers, etc. Took only 20 or so minutes.

But just a suggestion.

I also did one with jetstream just to get familiar with it's Auth scaffolding.

@thewebartisan7

It's possible to use laravel UI views with Fortify, it's a good start point to change frontend. I showed it in this french article.

@jlrdw the problem was not upgrading to Laravel 8, because already existed Laravel UI legacy package (I found 2), and it was pretty easy as you said to migrate Laravel UI to Laravel 8. But since I am working on a commercial application, I want to upgrade to Laravel 8 keeping what it offer. So I wanted to implement Fortify, but without Jetstream, since I don't like too much the TALL stack.

@bestmomo I implement all features of Jetstream not only what Fortify offer, I implement 2 Factors Auth, Loggout from other sessions, Avatar crop and upload, delete users and even Socialite, that I already used with Laravel UI. If you ony implement login, register and forgot password, that is more quick I agree, in fact there are already 2-3 package that do that. But if you implement all features of Jetstream that is a bit more complicated. First you need to understand the logic behind it, and then implement it. Then consider that I also do it for Bootstrap 5 and UIKIt 3. And all form are in ajax, without page reloading, with vanilla JS and axios.

@thewebartisan7

So you made Jetstream without Jetstream :)

@bestmomo haha I like that slogan, can I use it?

I'm a non-professional, new to Laravel and to webdev and programming in general. Most of this discussion is over my head.

As personal projects, I made one project in Laravel 6 upgraded to 7, and now am working on a similar project in L8 with Jetstream. I'm not familiar enough with the framework to even spot the differences with Jetstream beyond seeing that the directory structure is different, Jetstream & Livewire add components. I've read the Fortify and Jetstream (and Livewire too) docs and watched the series, but still not sure what's actually new that I should be seeing or struggling(?) with. I also watched most of Taylor's talk.

What is different that would cause a new guy problems, delays, extra effort?

What are the main objections to Jetstream?

What is there new to take advantage of that L7 didn't offer?

Thanks

Jetstream offers and scaffolds a couple of different stack options, but the problem there is what if you're not using any of that. So the point is you can still use laravel UI to scaffold Authentication.

For example I use fetch Js, and plain vanilla Js.

You have to remember all of that is optional. For example someone might use react instead of vue.

@jlrdw

If I used standard UI in my previous project (L7) and now using Jetstream / Livewire, should I notice any differences or have any extra difficulties? (I haven't gotten to views yet in current project other than dashboard and registration/login. In my L7 project I just had some standard blade views with Bootstrap, and I added some CSS Grid to it.)

Well you could do what I did, do a new project just to play around with the various features and check them all out. It could be a project just for playing around with the new features.

Yep, that's what I'm doing. I (think I) understand from reading that Jetstream/Fortify installs auth scaffolding. But from what I experienced, so does UI. Login/register links are on splash page. Is it something deeper that I'm missing or not understanding? Thanks for your patience.

Just remember you can redesign those screens anyway you like. For example in one app I have admin and bookkeeper roles. I redirect to their area depending on role.

It's a little involved, I won't go into details, but you might have one person who is admin and bookkeeper.

In such a case they are redirected to admin area, but a link is shown to bookkeeping. The link is only shown if they have both roles. Nothing a small if statement doesn't take care of.

You have to remember also that when the scaffolding takes place, it's only meant as a starter, I'm sure Taylor figured Developers would redesign to their custom needs.

I find it pretty easy to take one panel, duplicate it, and do the final design in one for admin, and the other bookkeeper.

Also I definitely use Authentication for a login is required, and use authorization to determine what that logged in person can or cannot do.