The mobile app is already live with a Flutter front-end and a PHP Laravel back-end, and both layers now need attention in equal measure. Source code is tracked in Git and builds are automated through CI/CD, so you will be working against clearly defined branches and staging servers. Front-end tasks centre on improving the current Flutter codebase so the UI feels smoother and the overall performance is more consistent across Android and iOS. On the server side, the Laravel project requires the same depth of care—refactoring where necessary, tightening security, and making sure every existing endpoint responds quickly and reliably to the updated client. You will have direct access to: • Flutter project repo (Dart, latest stable channel) • Laravel 9 repo (PHP 8+, MySQL) Deliverables • Updated Flutter project that compiles without warnings and runs on both major platforms • Refreshed Laravel code pushed to the main branch, with all unit tests passing • Brief change log summarising what was touched on each side of the stack Acceptance criteria 1. No new critical or high-severity issues introduced. 2. All basic user flows verified on staging (login, data fetch, form submission). 3. Response times on key API endpoints remain under existing thresholds. Feel free to suggest incremental milestones that make sense for you—feature blocks, sprint cycles, or per-module hand-offs work for me as long as both the Flutter front end and Laravel back end move forward together.