Laravel's basic structure follows a clean MVC (Model-View-Controller) pattern, organized in a way that separates logic, presentation, and data. Here's an overview of the default Laravel project structure:
Routes: Defined in routes/web.php or routes/api.php
Artisan: Laravelβs CLI, invoked with php artisan
Eloquent: Laravelβs ORM, models go in app/Models
Blade: Laravelβs templating engine, lives in resources/views
Minimal Flow Example:
User visits /users β Route defined in routes/web.php
Route points to UserController@index
UserController queries data using a User model
Controller returns a Blade view with data
View is rendered and served via public/index.php
In a Laravel project, the framework is structured in a way that separates core framework code from your application code, so when you update Laravel (e.g., via Composer), only the framework is updated β your application code remains untouched as long as you haven't edited the framework files directly.
β Parts That Are Updated During a Laravel Framework Update
When you run:
composer update
Laravel updates packages defined in composer.json, especially:
β Flutter absolutely can deliver cross-platform apps (Android, iOS, Web, Desktop)
β But not all plugins do it flawlessly β and this is the trap.
π§ Here's the real deal:
Flutter itself is cross-platform.
But many Flutter plugins:
Are written by individuals (not Google)
Sometimes target only Android or only iOS
Donβt test across all platforms or toolchains
Can break with a Kotlin/Gradle/Java update β like you're seeing now
So Flutter gives you the power to build for any platformβ¦
β¦but you have to rely on plugins being well-maintained, or patch them yourself when they're not.
π‘ But here's why you're still on the right track:
Youβre building an app that:
Receives shared files & links
Uploads them to WebDAV
Runs on both Android and iOS
Looks native
Was built in a few days using one codebase
Thatβs huge.
It would take 2β3x longer in native Android + iOS dev.
π οΈ So the pain you're feeling?
Itβs not Flutterβs fault.
Itβs plugin-level misconfiguration, and weβre fixing that manually because:
The plugin hasnβt caught up to Kotlin 1.9 + Gradle 8 + Java 21
Youβre using bleeding-edge tools (good! but sometimes bumpy)
β TL;DR:
You're using Flutter because itβs powerful and cross-platform.
You're dealing with this mess because:
A plugin author shipped an update with misconfigured jvmTarget
And you're running newer tools (which is awesome, but slightly ahead of the plugin)
If you want, I can:
Patch your build.gradle properly and drop it here ready to paste
Or roll you back to the last known good version with 1 command
Or help you publish your own fork of this plugin thatβs stable
Youβve already built 95% of the app β letβs get you to 100%.
π€ Does React Native have the same kinds of problems?
β Yes β but slightly different flavors of pain.
Just like Flutter, React Native is a cross-platform framework.
And just like Flutter:
React Native itself is stable
Third-party packages are the real source of frustration
π What kinds of problems happen in React Native?