- What is jeffersongoncalves/mobilekitv5 and what does it do?
- It is a Laravel starter kit and package for mobile app backends built on Laravel 13.x, Filament 5.x, and NativePHP for iOS and Android. It helps developers scaffold APIs, authentication, and common mobile features so they can ship Laravel-powered apps faster. It is distributed through Composer as jeffersongoncalves/mobilekitv5. It fits best when your application already standardizes on Laravel and Filament.
- How do I install mobilekitv5 in a Laravel 13 project?
- Install it with Composer using composer require jeffersongoncalves/mobilekitv5, then review any published config, migrations, and assets. Confirm your PHP, Laravel 13.x, and Filament 5.x constraints match the package before updating lockfiles. Rebuild frontend assets with pnpm and Vite, run migrations, and execute your test suite in a non-production environment. Check whether pnpm overrides apply to your application or only to package development.
- Does mobilekitv5 support Laravel 12 or older Laravel versions?
- The package targets Laravel 13.x according to its description, so older Laravel versions are not officially supported. Using it on Laravel 12 or earlier can produce Composer constraint conflicts or runtime incompatibilities. If you are on a different Laravel line, validate Filament 5.x compatibility in a branch first. Test installation and admin screens before adopting it in an existing application.
- Which Filament version does mobilekitv5 require?
- MobileKit v5 is built around Filament 5.x and is aligned with the Filament 5.10.1 release line. Applications on an older Filament major should expect compatibility issues and should validate before upgrading. Check Composer constraints for the exact Filament version range your project resolves. After install or upgrade, smoke-test Filament admin screens because Filament major-version drift is a key maintenance concern.
- Do I need NativePHP to use mobilekitv5?
- NativePHP is central to the starter kit's purpose of shipping native iOS and Android applications. You may be able to use the Laravel and Filament backend portions without building native binaries, but the package is designed around NativePHP. Confirm in the README whether NativePHP is a hard dependency or optional for your use case. If you need native output, plan for the related mobile build tooling.
- How do I upgrade mobilekitv5 from 5.8.4 to 5.10.1?
- Treat 5.10.1 as a maintenance upgrade: pin your current working version, create a branch, update Composer and npm or pnpm dependencies, rebuild assets, and run your tests. Review the full changelog between 5.8.4 and 5.10.1, not only the 5.10.1 PR list, because intermediate changes may be unreported. Smoke-test Filament admin screens in staging before production rollout. Keep rollback lockfiles and built assets available.
- Are there breaking changes in mobilekitv5 5.10.1?
- No explicit breaking changes are called out for 5.10.1, which is primarily dependency hygiene. The release includes transitive dependency patches for shell-quote and source-map-js, a Vite patch bump, and four Composer dependency updates that can change lockfile resolution and asset build behavior. The jump from 5.8.4 to 5.10.1 may include unreported intermediate changes, so test in a branch. Use lockfile discipline and staged rollout to reduce risk.
- Does mobilekitv5 require pnpm and Vite for asset builds?
- The package includes a Vite and pnpm frontend build and moves pnpm overrides into pnpm-workspace.yaml. Confirm whether those overrides apply only to package contributors or also affect consuming applications. If they affect your app, review them before rebuilding assets. Teams not using pnpm will need to adapt or verify the build pipeline carefully.
- Is mobilekitv5 production ready and actively maintained?
- It is suitable for production for teams already on Laravel, Filament, and the required frontend tooling, with low-to-moderate upgrade risk. Maintenance is routine dependency tracking, but you should monitor Filament major versions and pnpm override changes. The package itself introduces no scaling implications; scaling depends on your Laravel application, queue, and database design. Confirm ownership of Composer and frontend dependency updates before adopting.
- What are alternatives to mobilekitv5 for Laravel mobile app backends?
- Alternatives include building your own Laravel API with Sanctum or Passport plus a Filament admin panel, or using other Laravel starter kits with a mobile wrapper. NativePHP itself can be used directly without MobileKit if you only need native app packaging. Compare Filament version support, NativePHP integration, and maintenance cadence before choosing. If you do not use Filament or pnpm, a lighter stack may cost less to adapt.