What we do
Tools
Industries
Department
How we workLet's talk →
Home/Hire a Laravel Developer
Laravel Development

Hire a Laravel Developer for the App You Already Run

Laravel usually gets picked because off-the-shelf software couldn't handle the business's own rules. Years later the same app is still running, the person who built it has moved on, and it's a few versions behind, slower with real data, or quietly failing at the background work nobody sees. Most people hiring a Laravel developer are in one of those three spots.

Which one sounds like your app?

Behind on versions. The framework in composer.json is several majors old, and packages refuse to update. You need a stepwise upgrade, covered below.

Slow now that the tables are big. Screens that were instant take seconds. Usually a few Eloquent queries, not the whole app.

Things silently don't happen. Emails, exports or order updates go missing. That's almost always the queue or the scheduler.

How Laravel queues fail without anyone noticing

A queue moves slow work, like emails, PDFs and calls to other systems, out of the web request. When it stops, the website still loads, so nobody sees it until a customer complains.

The workers died and nothing restarted them

How you'll know: Jobs pile up in the jobs table or in Redis, and nothing is processed until someone logs in and runs a command.

Fix: Run the workers under a process monitor such as Supervisor, as the Laravel docs describe, so a crashed worker comes straight back.

A deploy went out, but the workers run the old code

How you'll know: A fix works on the website but not in emails or background jobs, or jobs start throwing errors right after a release.

Fix: Workers are long-running processes that keep the code they started with. Add php artisan queue:restart to every deploy.

Failed jobs pile up where nobody looks

How you'll know: The failed_jobs table has hundreds of rows going back months.

Fix: List them with php artisan queue:failed, fix the cause, retry with queue:retry, and send an alert when new failures appear. Horizon gives a dashboard for this if you use Redis queues.

Long jobs run twice

How you'll know: Customers get two copies of an email or two charges, usually on the slowest jobs.

Fix: The worker timeout has to be shorter than the queue's retry_after setting, or a second worker picks the job up while the first is still running. Make jobs safe to run twice as well.

Scheduled tasks stopped after a server move

How you'll know: Nightly reports or reminders just stopped, around the time the app changed hosts.

Fix: The scheduler only runs if one cron entry calls php artisan schedule:run every minute. It's easy to leave off a new server.

Bringing an old Laravel app up to date

Laravel ships a major version roughly once a year, each with its own upgrade guide. Skipping straight to the newest one is how upgrades go wrong.

  1. 1

    Write tests around what the business depends on

    Logging in, placing an order, the admin actions staff use daily. If the app has no tests, a handful of these is enough to tell you whether an upgrade broke anything.

  2. 2

    Go one major version at a time

    Follow each version's upgrade guide in order, run the tests, and deploy before starting the next. Laravel Shift, a paid service, automates much of each step and is worth considering for big jumps.

  3. 3

    Deal with the packages

    Old apps often depend on packages that were abandoned. Each one gets updated, replaced, or its code brought into the app.

    Watch for: the PHP version. Newer Laravel needs newer PHP, so the server usually moves too. The PHP-only side of that is on our PHP developer page.

  4. 4

    Fix the slow queries while you are in there

    Turn on Model::preventLazyLoading() outside production to catch N+1 queries, add eager loading with with(), and add the indexes the slow screens need. Profile against a copy of real data, not a test database with a hundred rows.

Reading the custom logic before changing it

The part of a Laravel app that matters is the part nobody else has: the pricing rules, the approval steps, the way it talks to the accounting system. Before we change anything, we read through that logic and the queues and queries around it, and write down what it does. That's what makes the upgrade safe, and it's what the next developer will need too.

Laravel is often the backend for other things, like a mobile app or partner integrations through an API. If that's where your project is heading, see API developer and backend developer, and custom software development if you're deciding whether to build something new at all.

Let's talk

Your Laravel app, current and running its background work

n-frames takes over existing Laravel apps with its own developers: we upgrade them version by version, fix the queues and slow queries, and keep the custom logic documented. New features get built on a codebase that's up to date, not one held together by old packages.

Upgrade Laravel one version at a time →

Questions people ask

Can you take over a Laravel app a previous freelancer built and left?

Yes, it's routine. We start by getting it running locally, checking which Laravel and PHP versions it's on, and looking at how its queues and queries perform with real data, before changing anything.

Our admin panel is slow now that we have real data. Can you fix that?

Usually, and without a rebuild. Slow admin screens are most often a few queries loading related records one at a time or missing an index. We measure first and fix those.

Does a small Laravel fix really need an agency like n-frames?

Not always. A small, contained fix on a healthy app is a small job and we'll quote it as one. Most of what reaches us turns out to be tied to an old version or a fragile queue, which is bigger.

Is the free quote actually free, with no strings?

Yes. You get an honest number for the work, including the upgrade path and the custom logic, which is where the real effort usually is.

Is it cheaper to rewrite the app than upgrade it?

Rarely. A rewrite has to rediscover every business rule the old app quietly handles. Upgrading in steps keeps the app running the whole time and costs less in most cases we see.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.