At this point, I only have complaints rather than solutions.
Maybe we should have a data layer accessible via API that device-specific (meaning mobile, not OS specific) UIs utilize?
I don't know. You all are smarter than me, so figure it out and fill me in.
I absolutely believe that websites should be responsive, however, there are strong arguments that mobile/tablet-specific versions of sites are a good idea.
In general, I dislike a lot of the modern web, but I find the mobile web to be extremely annoying and cumbersome.
I understand the argument that having multiple versions of a site creates more work. I would argue that trying to create a one-size/one-experience-fits all solution creates a ton of unnecessary work and gives your user's a lackluster experience.
Donโt you love it when something isnโt working and you stare at the code, and stare, and stare, and it was something incredibly stupid causing the problem?
Itโs frustrating, of course, but the absurdity makes me smile.
.@laravelphp friends, quick question: In the request lifecycle, are ServiceProviders (core/custom) bootstrapped before or after the request goes through middleware (core/custom)? I thiiiink I know, but I also think I might be over-thinking it. I think.
Iโm doing research into code reviews and Iโd like your input. What is your experience with it? Likes/dislikes? How does your team implement reviews? Reply here for email [email protected]
Please RT for reach!