Mobile apps powered by Laravel

Turn your Laravel app into a mobile app

Get native iOS and Android apps built on your Laravel app, with nothing to rebuild. Every update you deploy shows up in the app too.

Train the Mind's app, with a mental performance lesson for athletes OneHE's app, with its welcome screen for educators ATL311, Atlanta's city services app, with quick links to service requests

2,000+ apps published since 2013

BestsellerJohn VarvatosOnlyBuyBuyBabyBoozeBudJack & JonesRiot FestPerfume.com
BestsellerJohn VarvatosOnlyBuyBuyBabyBoozeBudJack & JonesRiot FestPerfume.com
BestsellerJohn VarvatosOnlyBuyBuyBabyBoozeBudJack & JonesRiot FestPerfume.com
BestsellerJohn VarvatosOnlyBuyBuyBabyBoozeBudJack & JonesRiot FestPerfume.com

Everything carries over

Everything your Laravel app does, on iOS and Android

The mobile app runs on the Laravel app you deploy today, so your pages, logins, data and notifications all work in it. There's no second app to build or keep in sync.

Your pages, as they are

Blade, Livewire or Inertia pages look and work in the app just as they do on the web.

Routes and navigation

Every route you have today works in the app, with native navigation on top.

Login as you have it

People stay signed in through the same sessions, whichever auth package you use.

Your data

Every screen reads the same database through the same code, so there's no second copy on the phone.

Notifications

The notifications and queued jobs you already send can reach app users as push through OneSignal.

Live updates

Real-time updates arrive in the app just as they do in the browser.

Your front end

Tailwind, Alpine and whatever else you build with look the same in the app.

Deploys

Deploy with Forge, Vapor, Laravel Cloud or your own pipeline, and the app shows each release as soon as it goes live.

For your developers

Your Laravel code knows when it's in the app

Your Laravel app can tell when someone opens it in the mobile app, so you can change what app users see or add pages just for them. This middleware makes that check once and shares it with every view.

  • Blade that knows about the app

    Use @if ($inApp) or @unless ($inApp) anywhere, from layouts to Livewire components, to change what app users see.

  • Push from your notification classes

    Link each device to the user's ID after login, then send push through OneSignal from your queued notifications.

  • Routes just for app users

    Register app-only pages, like onboarding or member offers, with your usual controllers and middleware.

  • Login screens that follow your auth

    Close the app's login screen after a successful login and bring it back on logout, whichever auth package you use.

Learn more about native functions

app/Http/Middleware/DetectMobileApp.php
<?php

namespace App\Http\Middleware;

use Closure;
use Illuminate\Http\Request;
use Illuminate\Support\Facades\View;

class DetectMobileApp
{
    public function handle(Request $request, Closure $next)
    {
        // The MobiLoud app adds "canvas" to its user agent
        $inApp = str_contains(
            strtolower($request->userAgent() ?? ''),
            'canvas'
        );

        // Any Blade view can now check $inApp
        View::share('inApp', $inApp);

        return $next($request);
    }
}

MobiLoud vs the alternatives

Build a second app, or use the one you have

NativePHP puts a separate copy of your app on every phone. The API route means writing a new app from scratch in Flutter or React Native. Either way, you end up with two apps to maintain. MobiLoud builds on the Laravel app you already run.

MobiLoud

  • Built on the Laravel app you deploy
  • Blade, Livewire and Inertia views as they are
  • One database, on your own servers
  • No native app development required
  • Live in 6 to 8 weeks

NativePHP

  • A separate copy of Laravel on every phone
  • A local SQLite database, synced through an API
  • Views rebuilt as NativePHP components
  • Xcode, Android Studio and signing to manage
  • A store release for each code change

Sanctum, then Flutter or React Native

  • API endpoints for every screen
  • Sanctum tokens for the app, sessions for the web
  • A second front end, written from scratch
  • Two codebases shipping on two schedules
  • Mobile developers to hire

The operating model

You ship Laravel. We ship the apps.

Your team keeps building in Laravel, the same way as today. We build the iOS and Android apps, keep them up to date with each new OS version, and look after everything app-specific.

Your team

Stays in Laravel

  • Features, fixes and migrations, deployed as usual
  • Separate Blade views for the app, where they help
  • Push sent from your own notification classes
  • Decisions about what ships next

Our team

Builds, ships and updates the apps

  • The iOS and Android apps themselves, from build to upkeep
  • Every store submission, from first launch to the latest update
  • New iOS and Android versions, handled as they arrive
  • OneSignal, deep link and analytics setup
  • Native SDK integrations when you need them (Enterprise)
  • A dedicated success manager and an SLA (Enterprise)

Getting live

Live in both app stores 6 to 8 weeks from kickoff

Your team is needed at two points: the kickoff and the sign-off. The native work between them is ours.

  1. Week 1

    Kickoff

    Your developers walk us through the app: which routes belong in the tab bar, which auth package you use and what app users should see differently. Then you invite us to your Apple and Google developer accounts.

  2. Weeks 2 to 3

    Build and integrate

    Working from your production URL, we set up the tab bar, push notifications and deep links for your named routes. A test build is on your phone in week two.

  3. Week 4

    Customize and test

    We test logins, forms and Livewire interactions on real devices, fine-tune the splash screen and back button, and connect GA4 and Firebase before sign-off.

  4. Weeks 5 to 8

    Launch

    Submission goes out from your developer accounts. Review by Apple and Google usually takes one to two weeks, and we handle any questions. From then on, deploying Laravel updates the app.

For the people who sign it off

We can deliver everything your legal, security and finance teams will ask for:

  • Data Processing Agreement and GDPR documentation
  • An SLA with 24/7 support and an uptime commitment (Enterprise)
  • Custom contracts, redlines and payment terms
  • Payment by invoice or bank transfer
  • User data stays in your own systems

Common Laravel questions

Have any more questions we didn't answer? Book a 30-minute call or send us a message to clear it all up.

Book a call
Do we need NativePHP?

No. NativePHP puts a separate copy of your Laravel app on each phone, with its own SQLite database that syncs through an API, and since version 4 its screens are built from NativePHP's native components. MobiLoud builds native apps on your live Laravel app, with your existing views and one database.

Does it work with Livewire and Inertia?

Yes. Livewire components, Inertia pages with Vue or React, and plain Blade views all work, including real-time updates over Reverb or Pusher.

Do we need an API for the app?

No. The app loads the pages Laravel already renders, so your routes, controllers and session auth work as they are. You only need an API if you want one for something else.

Will our auth still work?

Yes. Breeze, Jetstream, Fortify and custom guards work because the app uses your normal web sessions, and users stay signed in between visits. For Google sign-in, we set up the native handling Google requires.

How do push notifications work?

Through your own OneSignal account, or Klaviyo on the Enterprise plan. After login, one JavaScript call links the device to the user's ID, so your notification classes and queued jobs can send push through OneSignal's REST API.

Will it feel like a native app?

Yes. Your views still come from Laravel, and we add what makes it an app: a native tab bar and navigation, push notifications, persistent login, deep links, a splash screen and haptic feedback, with details like the back button tuned for mobile.

Will Apple approve it?

Yes. App store review is part of our job: we've taken more than 2,000 apps through it since 2013. The native navigation, push notifications and persistent login we add meet what Apple expects, and we reply to the reviewers for you.

What does it cost?

The Business plan is $1,499 a month, or $1,274 a month billed annually, plus a one-time fee to build and publish the apps, with up to 10,000 monthly active users. Enterprise, with native SDK integrations, a dedicated success manager and an SLA, is custom-priced. Neither plan takes a share of your revenue.

How long does it take to launch?

Most teams are live in 6 to 8 weeks: four weeks to build, test and approve the apps, then one to two weeks of app store review. Your team can keep deploying the whole time.

Who owns the app and the code?

You do. The listings are under your own Apple and Google developer accounts, and your Laravel code is yours alone. MobiLoud owns the intellectual property in the platform that builds the native apps, and if you ever leave, you keep your listings and your users.

See your Laravel app as a mobile app

We'll build a free, interactive preview of your app, so you can see how your Laravel app looks and works on iOS and Android.