Mobilekit Laravel Package

Product Decisions This Supports

• Build vs. buy for mobile delivery. MobileKit bundles Laravel + Filament + NativePHP into a starter kit, so it answers a recurring PM question: do we staff a mobile app from scratch, or ship our existing admin/product surface to a native shell? This release keeps that bundle current (NativePHP 4.2.0 → 4.3.0, Filament 3.3.56), which is the signal you need before committing a quarter of roadmap to it.
• Roadmap sequencing for "one backend, two clients." The notable functional change here is "Use user/admin packages for models, resources and login" — the kit is extracting user and admin concerns into separate installable packages rather than inlining them. For a PM this reads as the project maturing toward composable parts: you can adopt the admin/Filament layer without inheriting the mobile scaffolding, and vice versa. That materially lowers the cost of a phased rollout (web admin first, native app second).
• Platform currency / upgrade risk. Fix composer.json description to Laravel 13 plus PHPStan now running on PHP 8.4 tells you the package is tracking the leading edge of the framework. Useful when your platform team is deciding whether to greenlight a Laravel 13 upgrade this cycle: a starter kit already on it is a small de-risking data point.
• Use cases this is a fit for: internal tools and field-ops apps where the admin UI already lives in Filament; MVPs where a single Laravel codebase shipping web + native is worth more than best-in-class native UX; teams already fluent in the TALL/Filament stack.

When to Consider This Package

Adopt as a starting point or reference architecture, not as a vendor dependency:

• You are already on Filament and want a native shell without rebuilding auth, user/admin models, and resources.
• You need a fast proof-of-concept for a single-codebase mobile play, and you accept that the scaffolding is opinionated.
• You want to read it — the user/admin package split is a reasonable pattern to copy even if you don't install the kit.

Look elsewhere (or budget for a fork) if any of these hold:

• Bus factor matters. This is a single-maintainer repository (@jeffersongoncalves). The bulk of this release is Dependabot noise plus self-authored CI standardization and sponsor-link chores — healthy hygiene, but not evidence of a contributor base or a support contract.
• You need release-note discipline. 3.3.56 is titled "Bump Filament," yet it also moves NativePHP, restructures user/admin models, patches shell-quote and source-map-js via pnpm overrides, and changes the Composer description to Laravel 13. Patch-level versioning here does not reliably signal scope, so treat every bump as potentially behavioral and pin versions.
• Native parity is a hard requirement. NativePHP is a maturing runtime; if you need deep native module access, platform-specific UX, or app-store-grade performance, a starter kit won't substitute for a native team.
• You need an LTS/support commitment. There is no visible deprecation policy or versioning contract.

How to Pitch It (Stakeholders)

To executives (one paragraph): MobileKit is an open-source Laravel starter kit that lets one PHP codebase serve both our web admin and a native mobile app. Evaluating it costs days, not weeks, and it could remove the "we need a second engineering team" line item from the mobile proposal. The trade-off is concentration risk: it's a single-maintainer project, so we'd fork and pin rather than depend on upstream, and we should not treat the latest patch release as a stability guarantee — the 3.3.56 notes mix dependency bumps with an internal restructure of the user/admin layer under a patch version.

To engineering: Version 3.3.56 is maintenance-weighted — Dependabot batches across Composer, npm and GitHub Actions, standardized CI/test/dependabot workflows, PHPStan moved to PHP 8.4, and an auto-merge rule for minor/patch action updates. Two items deserve a real look before we upgrade: (1) the move to user/admin packages for models, resources and login, which changes where auth and Filament resources are sourced from and is the only change here with plausible breaking impact on anything we've built on top; and (2) pnpm overrides migrated to pnpm-workspace.yaml with patches applied to shell-quote and source-map-js — supply-chain mitigations worth mirroring in our own pipeline. Recommendation: spike on a branch against 3.3.56, verify the login/resource wiring, and pin the tag if it holds.